Connect Continue to Nodes2Cloud

Continue's agent mode, through the local n2c-mcp proxy.

Continue 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.

Use a Personal Access Token

Continue connects with a Personal Access Token. 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.

Create .continue/mcpServers/nodes2cloud.yaml

yaml

Project.continue/mcpServers/nodes2cloud.yaml

name: Nodes2Cloud
version: "0.0.1"
schema: v1
mcpServers:
  - name: nodes2cloud
    type: stdio
    command: npx
    args:
      - "-y"
      - n2c-mcp
    env:
      N2C_API_KEY: n2c_pat_YOUR_TOKEN

Or let the installer write it

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

npx -y n2c-mcp@latest install --client continue --token n2c_pat_YOUR_TOKEN

Every flag is on the MCP setup page.

Good to know

Continue drops custom headers on remote servers, so this uses the local proxy (needs Node.js).
MCP tools only run in Agent mode.

Continue's MCP documentationInstructions checked 27 October 2026