Zed is a high-performance, collaborative editor from the team behind Atom. MCP is supported as 'context servers', configured in `~/.config/zed/settings.json` under a `context_servers` key. The inner shape is slightly different from Claude Code (command is an object with `path`/`args`/`env` fields). Best choice for speed-sensitive engineers and teams that want collaborative AI editing.
High-performance collaborative editor with AI panel and native MCP support (called 'Context Servers')
~/.config/zed/settings.json{
"context_servers": {
"github": {
"command": {
"path": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..."
}
}
},
"postgres": {
"command": {
"path": "npx",
"args": ["-y", "@modelcontextprotocol/server-postgres"],
"env": {
"POSTGRES_URL": "postgres://user:pass@host:5432/db"
}
}
}
}
}Real secrets should never be committed — use environment variables or your editor's secrets manager.
Zed's collaborative editing + GitHub MCP = pair programming with AI opening PRs on the fly.
Zed's speed shines on DB-heavy work — querying Postgres via MCP feels nearly instant.
Same reasoning — Zed + Supabase MCP makes schema exploration lightning-fast.
Zed's performance + Docker MCP = managing containers without lag. Great for infrastructure work.
Quick Stripe lookups while coding billing flows — Zed's minimal UI keeps focus on the code.
Ticket-to-code flow that feels snappy. Zed's keyboard-first UX pairs well with Linear's hotkeys.
Read specs in the Zed AI panel without switching windows. Perfect for spec-driven work.
Zed's AI panel summarises Sentry traces cleanly — great for quick triage.
Pull docs into Zed's context. Useful for unfamiliar libraries where RTFM is required.
Quick web search without leaving Zed. Tavily's LLM-tuned results work naturally with Zed's AI panel.
GitHub MCP first. After that: Postgres/Supabase for data (Zed's speed shines here), Linear for tickets, Docker for infra work. Same top picks as other editors, just in Zed's config shape.
In the main settings file: `~/.config/zed/settings.json` (or via Cmd/Ctrl+, → 'Open Settings JSON'). Use the `context_servers` key. No separate file like other editors.
Historical naming — Zed adopted MCP when it was still called 'context servers' internally. The feature is the same as MCP; only the key name differs. Future Zed versions may alias to `mcpServers`.
Yes via `.zed/settings.json` in the project root. Project settings merge with user settings; per-project context_servers override or extend global ones.
MCP invocations happen on the host's machine (the person who opened the session). Collaborators see results in the shared buffer but don't run MCPs on their own machines. Plan secrets accordingly.
Pick from the top 10 curated above, or browse the full marketplace of 100+ MCPs.