Zed

Zed calls MCP servers context servers and keeps them under context_servers in settings.json, which the zed: open settings command opens. The same servers can be added from Settings, AI, MCP Servers with the Add Remote Server button. A local server has a command; a remote one has a url.

Without a key

{
  "context_servers": {
    "wellworn": {
      "url": "https://mcp.wellworn.dev/mcp"
    }
  }
}

With a key

{
  "context_servers": {
    "wellworn": {
      "url": "https://mcp.wellworn.dev/mcp",
      "headers": { "Authorization": "Bearer ww_your_key" }
    }
  }
}

Confirm it works

Open Settings, AI, MCP Servers and watch the indicator dot next to Wellworn. Once it is up the eight tools are available to the Agent Panel.

What breaks

When a remote server has no Authorization header, Zed offers the standard MCP OAuth flow. Wellworn does not run an OAuth server, so starting that flow talks to nothing. On the no-key tier, leave the header out and dismiss the prompt rather than trying to authenticate.

If your Zed build predates remote context servers, bridge it through stdio:

{
  "context_servers": {
    "wellworn": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.wellworn.dev/mcp"],
      "env": {}
    }
  }
}

Verified 2026-09-08 against zed.dev