Context7 MCP server in Zed context_servers, configured right.
Zed calls MCP servers "context servers" and configures them in settings.json — here's the exact entry for Context7 and the restart step that makes it stick.
Zed integrated MCP early but under its own vocabulary: servers live in a context_servers object inside the main settings.json, not in a dedicated MCP file. That means examples written for Cursor or Claude Desktop need translating before they work here.
Context7 — Upstash's documentation server, 57.1k GitHub stars — is worth the translation. It feeds Zed's Agent Panel current, version-specific library docs, so generated code matches the dependencies in your lockfile rather than the model's training snapshot.
Why add it to Zed's agent
Zed's Agent Panel can use MCP tools while editing your project. With Context7 attached, a request like "migrate this file to the new router API" can start with a real documentation fetch for the version you're on. As of mid-2026 the server's tools resolve a library identifier and return its docs; the upstash/context7 repo documents the current list.
The server is open source, free, installed from npm, and runs locally over stdio — Zed spawns it for you.
The settings.json entry
Open your settings with the "zed: open settings" command (or edit ~/.config/zed/settings.json directly) and add a context_servers object at the top level. The entry declares a custom server with the real package name, @upstash/context7-mcp:
{
"context_servers": {
"context7": {
"source": "custom",
"command": "npx",
"args": ["-y", "@upstash/context7-mcp"],
"env": {}
}
}
}Restart the Agent Panel and verify
Zed generally applies settings on save, but context servers are processes — close and reopen the Agent Panel (or restart Zed) so the server actually spawns. In the panel's server list, Context7 should show as running with its tools available to the active profile. The tool list on its Loomal marketplace listing, https://loomal.ai/marketplace/context7, is a quick external reference for what you should see.
Troubleshooting in Zed
Because the entry lives inside your full settings.json, a stray comma anywhere in the file can stop Zed parsing all of it — if the server never appears, validate the whole file, not just your new block. Zed surfaces settings parse errors in its log (zed: open log), which is also where context-server startup failures land.
If the server starts in a terminal but not in Zed, the editor's environment is missing Node: launching Zed from a shell once, or installing Node system-wide rather than via a shell-initialized version manager, resolves it. Also check the agent profile in use — tools can be enabled per profile, and a server that's running but unticked in the profile looks identical to one that's broken.
FAQ
How do I install Context7 in Zed?
Add a context_servers entry to ~/.config/zed/settings.json with source "custom", command npx, and args ["-y", "@upstash/context7-mcp"], then restart the Agent Panel so Zed spawns the server. No separate MCP file exists in Zed.
Why is the key called context_servers instead of mcpServers?
Zed adopted MCP under its own "context server" naming, so configs from other clients need the key and shape translated. The underlying protocol is standard MCP — only the settings schema differs.
Context7 shows as running but the agent never uses it. What should I check?
Open the Agent Panel's profile settings and confirm Context7's tools are enabled for the profile you're chatting with. Zed scopes tools per profile, so a server can be healthy yet invisible to your current conversation.
Does Context7 require payment or an account?
No — it's open source and runs without an account. An optional API key from Context7 lifts rate limits for heavy use; check their documentation for what's current.
More MCP servers for Zed.
Browse the live index with real, probed tool lists.