Skip to main content
Zed calls MCP servers “context servers” and configures them in the main Zed settings file.

​
File location

Open the command palette and run zed: open settings to open ~/.config/zed/settings.json (or the platform equivalent).

​
Config

Add a context_servers block: 
{
  "context_servers": {
    "versuno": {
      "command": {
        "path": "npx",
        "args": ["-y", "versuno-mcp"],
        "env": {
          "VERSUNO_API_KEY": "uk_live_xxx"
        }
      }
    }
  }
}
Note the nested command object. This is Zed-specific — other clients flatten command, args, and env onto the server block directly.

​
Reloading

Zed watches the settings file and reloads context servers automatically when it changes. If the server doesn’t appear, restart Zed.

​
Using it

Open Zed’s assistant panel. Versuno’s tools appear in the tool picker. Invoke them from your prompt:
“Pull my ‘code review system prompt’ asset from Versuno into the workspace.”

​
Troubleshooting

Zed logs context server errors to its log file, accessible via zed: open log. Filter for context_server to see stderr output. See Troubleshooting.