Connect GitHub Copilot CLI to Nodes2Cloud

The copilot terminal agent.

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

Add the server

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

Or add it to mcp-config.json

json

Global~/.copilot/mcp-config.json

{
  "mcpServers": {
    "nodes2cloud": {
      "type": "http",
      "url": "https://api.nodes2cloud.com/mcp",
      "tools": [
        "*"
      ]
    }
  }
}

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.

Add the server

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

Or let the installer write it

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

npx -y n2c-mcp@latest install --client copilot-cli

Every flag is on the MCP setup page.

Good to know

tools is required in the file; ["*"] enables every tool.

GitHub Copilot CLI's MCP documentationInstructions checked 27 October 2026