Connect Kilo Code to Nodes2Cloud

Kilo's CLI, VS Code and JetBrains builds share one config.

Kilo Code 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 Kilo Code first connects, your browser opens so you can sign in to Nodes2Cloud and approve access.

Add the server

kilo mcp add nodes2cloud --url https://api.nodes2cloud.com/mcp

Sign in

kilo mcp auth nodes2cloud

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 kilo.json

json

Global~/.config/kilo/kilo.json
Projectkilo.json

{
  "mcp": {
    "nodes2cloud": {
      "type": "remote",
      "url": "https://api.nodes2cloud.com/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer n2c_pat_YOUR_TOKEN"
      }
    }
  }
}

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

Or let the installer write it

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

npx -y n2c-mcp@latest install --client kilo-code --token n2c_pat_YOUR_TOKEN

Every flag is on the MCP setup page.

Kilo Code's MCP documentationInstructions checked 27 October 2026