Nodes2Cloud — Claude Code MCP server: setup
This MCP server lets an agent build and check workflows, then publish them as Cloudflare Workers in your account. Use it when automation needs agent-driven deployment.
claude mcp add --transport http mcp https://api.nodes2cloud.com/mcpWhat Nodes2Cloud does
Nodes2Cloud gives an agent tools for finding nodes, reading their schemas, creating workflows, and checking their graphs. It can manage saved versions, publish them as Cloudflare Workers, start runs, inspect logs, and pause or roll back deployments. There are 28 tools, and workflows with an MCP Tool trigger can be called as tools in their own right.
You can connect to the hosted service at https://api.nodes2cloud.com/mcp with OAuth 2.1, or run n2c-mcp as a local stdio bridge. A remote deployment waits for browser approval by default. Connections can also be limited to selected workflows, and deployment access can be disabled.
With the stdio setup, the installer puts the personal token in the client configuration as plain text, so keep that file out of version control. When N2C_API_KEY is missing, the server stays in preview mode: it exposes setup information instead of carrying out tool calls.
What it helps with
- assemble workflows from nodes
- check a graph before deployment
- publish versions as Cloudflare Workers
- start, pause, or stop runs
- inspect logs and roll back versions
Example prompts for the agent
- Build a workflow for this automation and validate its graph.
- Publish the checked version as a Cloudflare Worker after I approve it.
- Show the latest run status and its logs.
How to install Nodes2Cloud
1Platform CLI: remote server
claude mcp add --transport http mcp https://api.nodes2cloud.com/mcp2Platform CLI
claude mcp add --env N2C_API_KEY=<N2C_API_KEY> --env N2C_MCP_ENDPOINT=<N2C_MCP_ENDPOINT> --transport stdio nodes2cloud -- npx -y n2c-mcpReplace <…> with your own values
1Platform CLI: remote server
codex mcp add nodes2cloud --url https://api.nodes2cloud.com/mcp2Platform CLI
codex mcp add nodes2cloud --env N2C_API_KEY=<N2C_API_KEY> --env N2C_MCP_ENDPOINT=<N2C_MCP_ENDPOINT> -- npx -y n2c-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"nodes2cloud": {
"url": "https://api.nodes2cloud.com/mcp"
}
}
}{
"mcpServers": {
"nodes2cloud": {
"command": "npx",
"args": [
"-y",
"n2c-mcp"
],
"env": {
"N2C_API_KEY": "<N2C_API_KEY>",
"N2C_MCP_ENDPOINT": "<N2C_MCP_ENDPOINT>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"nodes2cloud": {
"type": "http",
"url": "https://api.nodes2cloud.com/mcp"
}
}
}{
"servers": {
"nodes2cloud": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"n2c-mcp"
],
"env": {
"N2C_API_KEY": "<N2C_API_KEY>",
"N2C_MCP_ENDPOINT": "<N2C_MCP_ENDPOINT>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http nodes2cloud https://api.nodes2cloud.com/mcp2Platform CLI
gemini mcp add -e N2C_API_KEY=<N2C_API_KEY> -e N2C_MCP_ENDPOINT=<N2C_MCP_ENDPOINT> nodes2cloud npx -y n2c-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Nodes2Cloud
How do I install Nodes2Cloud in Claude Code?
Run claude mcp add --transport http nodes2cloud https://api.nodes2cloud.com/mcp. The first connection opens a browser consent screen.
What does Nodes2Cloud do?
It lets an agent create, validate, publish, and operate workflows as Cloudflare Workers in your account. The available actions also cover runs, logs, versions, and rollback.
Can Nodes2Cloud work without an API token?
A full setup uses N2C_API_KEY, unless you connect to the remote server with OAuth. Without the key, the server lists its available capabilities and returns setup guidance instead of running tools.
