How to add an MCP server to Zed

Add MCP servers to Zed, which calls them context servers, from Settings, AI, MCP Servers or the context_servers key in settings.json.

Local servers: Yes; runs stdio servers
Hosted servers: Yes; connects by URL
Config: JSON; how servers are added
Picks: 5; ranked

Open Settings, AI, MCP Servers, click Add Server, and choose Add Local Server or Add Remote Server. Zed writes the entry under context_servers in your settings file, which you can open with the zed: open settings file action. You can also install many servers as Zed extensions. A remote server with no Authorization header gets an OAuth sign-in prompt.

Good for

Zed users who want the Agent Panel to reach docs, GitHub or a browser
People who prefer installing a server as a Zed extension
Developers using external agents who want Zed servers forwarded to them
Anyone who wants per-tool approval for MCP calls

Install Zed

Zed

1
Open Settings, then AI, then MCP Servers (or run the agent: open settings action).
2
Click Add Server in the page header.
3
Choose Add Local Server or Add Remote Server.
4
Check the indicator dot next to the server name: green with "Server is active" means it works.

Zed calls MCP servers context servers. The docs say Zed currently supports MCP's Tools and Prompts features.

From the vendor's docs. Source.

At a glance

Name for MCP servers: Context servers
Add a server: Settings, AI, MCP Servers, Add Server
Config key: context_servers in the settings file
Open the settings file: zed: open settings file
Local server fields: command, args, env
Remote server fields: url, headers
Sign in (OAuth): Prompted when a remote server has no Authorization header
Protocol features: Docs: currently supports Tools and Prompts; reloads the tool list on tools/list_changed
Tool approval: agent.tool_permissions.default: confirm (default), allow or deny
Per-tool rules: Key format mcp:<server>:<tool_name>
External agents: Zed forwards configured servers over ACP
Status check: Green dot, "Server is active"

Add an MCP server to Zed

1
Open the MCP settings
Go to Settings, AI, MCP Servers, or run the agent: open settings action and select MCP Servers.
2
Add the server
Click Add Server, then Add Local Server or Add Remote Server. Or install one as an extension: Add Server, Install from Extensions. Zed writes the entry to your settings file.
Uses Context7

Or edit settings.json

Run zed: open settings file and add:

{
  "context_servers": {
    "local-mcp-server": { "command": "some-command", "args": ["arg-1"], "env": {} },
    "remote-mcp-server": { "url": "https://example.com/mcp", "headers": { "Authorization": "Bearer <token>" } },
    "remote-mcp-server-with-oauth": { "url": "https://mcp.example.com/mcp" }
  }
}

Leave out the Authorization header if the server uses OAuth. Zed then prompts you to sign in.

4
Check it loaded
In Settings, AI, MCP Servers, look at the dot next to the server name. Green with the tooltip "Server is active" means it is running. Other colors explain what is wrong in their tooltip.
5
Use it in the Agent Panel
Name the server in your prompt. How reliably tools get called varies by model. To force a server, make an agent profile with only its tools turned on.
Prompt
```
Use the context7 server to look up the current docs for this library, then update my code to match.
```
Uses Context7
6
Tune tool approval
For the native Zed agent, agent.tool_permissions.default is "confirm" by default (Zed v0.224.0 and above), which prompts before any tool action, including MCP calls. Set a per-tool rule with the key mcp:<server>:<tool_name>, for example mcp:github:create_issue.

Best MCP servers for Zed

Official servers with an approved PlugWiki page that run in Zed over stdio or HTTP; ordered by GitHub stars, then name. Derived from data we hold.

MCP servers that work in Zed

40 · official first, then servers with a page, then by stars

Show all 40

Common errors and fixes

The status dot is not green
Cause: The server is not running. The tooltip says what is happening.
Fix: Read the tooltip, then check the command, args and env, or the URL and headers.
zed Source
A server needs more setup after install
Cause: Most servers require configuration, such as a Personal Access Token for the GitHub extension.
Fix: Follow the modal Zed shows after install, or the provider's docs for custom servers.
zed Source
The model does not call the server's tools
Cause: How reliably MCP tools get called varies from model to model.
Fix: Mention the server by name, or create an agent profile that turns off built-in tools and turns on only the server's tools.
zed Source
No OAuth sign-in prompt for a remote server
Cause: The entry has an Authorization header, so Zed does not start the OAuth flow.
Fix: Remove the Authorization header from the entry.
zed Source
An error from the server shows in the agent's answer
Cause: Zed passes the server's error message to the agent: bad parameters, server-side failures or unsupported operations.
Fix: Read the message and check the server's logs or docs for that error code.
zed Source

Verdict

Zed makes MCP setup simple with a settings page, extensions and OAuth, and its native agent asks before each tool call by default. The docs list Tools and Prompts as the supported MCP features, so check that your server needs nothing else.

Best for

Zed users who want one-click servers from extensions
People who want per-tool permission rules for MCP calls

Skip it if

You need Sampling, Elicitation or Discovery; the docs name them as areas where contributions are welcome

Questions

What does Zed call MCP servers?

Context servers. They live under the context_servers key in your Zed settings file.

Where is the Zed MCP config?

In your settings file. Open it with the zed: open settings file action. The MCP page does not state a path; the configuring-zed page shows ~/.config/zed/settings.json in an example.

Does Zed support remote (HTTP) MCP servers?

Yes. Choose Add Remote Server or add an entry with a url and optional headers.

Does Zed support OAuth for MCP servers?

Yes. If a remote entry has no Authorization header, Zed prompts you to sign in with the standard MCP OAuth flow.

Which MCP features does Zed support?

The docs say Zed currently supports MCP's Tools and Prompts features. Zed also reloads the tool list on its own when a server sends a notifications/tools/list_changed notification.

How do I know an MCP server works in Zed?

Open Settings, AI, MCP Servers and look at the dot next to the server. Green with "Server is active" means it is running.

Does Zed ask before running MCP tools?

Yes, by default. agent.tool_permissions.default is "confirm" for the Zed agent. Set it to "allow" to skip prompts or add per-tool rules.

Do external agents in Zed get my MCP servers?

Yes. Zed can forward configured servers to external agents over ACP, and those agents can also read their own native MCP config.

Can I install an MCP server as a Zed extension?

Yes. Run zed: extensions, or use Add Server, Install from Extensions. Many servers, including Context7 and GitHub, are available this way.

Information

updated Nov 2, 2026

Transports: stdio, Streamable HTTP
Config file (all): ~/.config/zed/settings.json (context_servers)
MCP docs: zed.dev

Website Docs

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3

Model Context Protocol · zed.dev
Installing Zed · zed.dev
Configuring Zed · zed.dev