Connect Goose to Nodes2Cloud

Goose desktop and CLI, as a remote extension.

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

Add to Goose

Opens Goose, which needs to be installed on this computer.

Or for one session

goose session --with-streamable-http-extension "https://api.nodes2cloud.com/mcp"

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 config.yaml

yaml

GlobalmacOSLinux~/.config/goose/config.yaml
GlobalWindows%APPDATA%\Block\goose\config\config.yaml

extensions:
  nodes2cloud:
    name: nodes2cloud
    type: streamable_http
    uri: https://api.nodes2cloud.com/mcp
    headers:
      Authorization: "Bearer n2c_pat_YOUR_TOKEN"
    enabled: true
    timeout: 300

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

Or let the installer write it

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

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

Every flag is on the MCP setup page.

Good to know

Goose names the field uri, not url.

Goose's MCP documentationInstructions checked 27 October 2026