MCP servers for Zed

Zed stores custom MCP servers under context_servers in settings. A remote server with no Authorization header starts an OAuth prompt. Tools and prompts are supported. This block was not run.

Docs: https://zed.dev/docs/ai/mcp

Config file: Zed settings, context_servers. Transports: stdio, http.

settings.json

Format example. We have not run this config.

{
  "context_servers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/absolute/path/you/allow"],
      "env": {}
    }
  }
}

Tested on Zed

No server is marked tested: true for this launch. There is no compatibility claim and no server detail page.

Not yet tested

These are well-known official servers seeded so the config shape is concrete. The label is the product: we have not installed them.

Server	Status	Auth	Risk
Filesystem Reference filesystem server from the MCP servers repo, shown in the Windsurf docs with an allowed directory argument. Repo	Not yet tested	None. Access is the directories you pass on the command line.	Reads and writes files under the paths you allow. Pass a narrow directory, not your home folder.
GitHub Official GitHub MCP server. VS Code’s Copilot docs show the remote endpoint https://api.githubcopilot.com/mcp. Repo	Not yet tested	GitHub account or token, depending on the endpoint	Can read and change repositories, issues, and pull requests for the account you connect. Review the scopes.
Playwright Microsoft’s Playwright MCP server, shown in the VS Code docs as a local npx command. Repo	Not yet tested	None for the local browser. The server launches a browser on your machine.	Drives a browser on the machine where it runs. Do not point it at accounts you would not open yourself.

Installing an MCP server can run code and reach the network. Pin a version and read the repo before you enable one. AgentPickr does not assume liability for servers we have not tested.