Connect Claude to Nodes2Cloud
Claude on the web, desktop and mobile, as a custom connector.
Claude 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 Claude first connects, your browser opens so you can sign in to Nodes2Cloud and approve access.
Add a custom connector
- Open claude.ai/customize/connectors (in the desktop app: Customize → Connectors).
- Choose + → Add custom connector.
- Name it Nodes2Cloud and paste https://api.nodes2cloud.com/mcp as the URL, then Add.
- Choose Connect and approve access in the browser.
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.
Claude Desktop, with the local proxy
- Add the entry below to claude_desktop_config.json, then restart Claude.
claude_desktop_config.json
json- GlobalmacOS
~/Library/Application Support/Claude/claude_desktop_config.json - GlobalWindows
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"nodes2cloud": {
"command": "npx",
"args": [
"-y",
"n2c-mcp"
],
"env": {
"N2C_API_KEY": "n2c_pat_YOUR_TOKEN"
}
}
}
}If the file already exists, add the nodes2cloud entry under mcpServers and keep what is already there.
Or let the installer write it
The n2c-mcp installer writes the same config into Claude's config file for you. Add --print to see it without writing anything.
npx -y n2c-mcp@latest install --client claude --token n2c_pat_YOUR_TOKEN
Every flag is on the MCP setup page.
Good to know
- A connector added on the web also appears in the desktop and mobile apps.
- On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
- claude_desktop_config.json only runs local servers, which is why the token path uses the proxy.