Connect Zed to Nodes2Cloud

Zed's agent panel, as a remote context server.

Zed talks to the Nodes2Cloud MCP server at https://api.nodes2cloud.com/mcp over Streamable HTTP. Once connected, your agent can read the node catalogue, write and check workflows, and request deploys that wait for your approval by default.

Sign in with your browser (recommended)

No token to copy. When Zed first connects, your browser opens so you can sign in to Nodes2Cloud and approve access.

Add it to settings.json

json

GlobalmacOSLinux~/.config/zed/settings.json

{
  "context_servers": {
    "nodes2cloud": {
      "url": "https://api.nodes2cloud.com/mcp"
    }
  }
}

If the file already exists, add the nodes2cloud entry under context_servers and keep what is already there.

Use a Personal Access Token

For headless machines and CI, or if you would rather not sign in through the browser. Create one in the editor under Integrations → MCP server → Headless & CI Tokens, then Generate Token. Replace n2c_pat_YOUR_TOKEN below with it.

Treat the token like a password and keep it out of source control.

Add it to settings.json

json

GlobalmacOSLinux~/.config/zed/settings.json

{
  "context_servers": {
    "nodes2cloud": {
      "url": "https://api.nodes2cloud.com/mcp",
      "headers": {
        "Authorization": "Bearer n2c_pat_YOUR_TOKEN"
      }
    }
  }
}

If the file already exists, add the nodes2cloud entry under context_servers and keep what is already there.

Or let the installer write it

The n2c-mcp installer writes the same config into Zed's config file for you. Add --print to see it without writing anything.

npx -y n2c-mcp@latest install --client zed

Every flag is on the MCP setup page.

Good to know

Zed's key is context_servers. With no Authorization header it runs OAuth.

Zed's MCP documentationInstructions checked 27 October 2026