Zed

Zed calls MCP servers context servers. They are configured in the same settings.json as the rest of the editor.

Add it

Open settings with ⌘, / Ctrl+, (or zed: open settings from the command palette) and add:

{
  "context_servers": {
    "vulnetix": {
      "source": "custom",
      "url": "https://mcp.vulnetix.com/mcp",
      "headers": {
        "Authorization": "ApiKey <orgId>:<hex>"
      }
    }
  }
}

Restart Zed.

Note Zed’s context-server schema has moved between releases. Some versions expect command/args for stdio servers and different keys for remote ones. If the block above is rejected, check Agent Panel → Settings → Context Servers in your build, or the Zed MCP docs, and keep the url and headers values identical to those above.

Confirm it works

Open the agent panel (⌘? / Ctrl+?). The context-server section should list vulnetix as running, with its tools available to the agent.

What is the EPSS score and SSVC decision for CVE-2021-44228?

Worth knowing

Agent panel only. Inline assist does not call MCP tools.

Project settings. .zed/settings.json in a repository works too, and the same warning applies as everywhere else: it is committed by default, so use the global settings file if the key would be literal.

Errors are in the log. Command palette → zed: open log.

Troubleshooting

Server missing from the panel. Most often a schema mismatch for your Zed version. See the callout above.

Runs but no tools. Check the URL ends in /mcp, then restart rather than reload.

401 in results. Both halves of the key.