Connect Cline to Nodes2Cloud

The Cline extension and the Cline CLI.

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

With the Cline CLI

cline mcp add nodes2cloud https://api.nodes2cloud.com/mcp --transport http

Or in the extension

Open Cline → MCP Servers → Configure → Configure MCP Servers.
Add the entry below, then choose Authorize next to nodes2cloud.

cline_mcp_settings.json

json

{
  "mcpServers": {
    "nodes2cloud": {
      "type": "streamableHttp",
      "url": "https://api.nodes2cloud.com/mcp"
    }
  }
}

If the file already exists, add the nodes2cloud entry under mcpServers 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.

With the Cline CLI

cline mcp add nodes2cloud https://api.nodes2cloud.com/mcp --transport http --header "Authorization: Bearer n2c_pat_YOUR_TOKEN"

Or in cline_mcp_settings.json

json

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

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

Good to know

type is required: without it Cline assumes the legacy SSE transport.

Cline's MCP documentationInstructions checked 27 October 2026