MCP servers in Zed

Zed registers MCP servers under a "context_servers" key in its settings.json, not the "mcpServers" key used by most clients. The integration is stdio-only, so reaching a remote server means bridging it locally with an mcp-remote command that Zed launches as the context server's process. There is no native remote transport or OAuth flow.

Where the config lives

macOS / Linux: ~/.config/zed/settings.json

Worked example: Fetch

Here's the exact config to add the Fetch MCP server to Zed. Every server in the directory has a ready-to-paste Zed config like this.

Add to ~/.config/zed/settings.json

~/.config/zed/settings.json

json

{
  "context_servers": {
    "fetch": {
      "source": "custom",
      "command": "uvx",
      "args": [
        "mcp-server-fetch"
      ]
    }
  }
}