Nodes2Cloud

Name: Nodes2Cloud
Author: nodes2cloud-com

by nodes2cloud-comversion 1.2.0i★ –iComputer or cloud

Registry namecom.nodes2cloud/mcp

Install

Overview

Description from the maker (original English)

Build, validate and deploy workflows as Cloudflare Workers in your own account, with approval.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Developer tools
You need to fill in: N2C_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: N2C_API_KEY, N2C_MCP_ENDPOINT

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://api.nodes2cloud.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "nodes2cloud": {
      "command": "npx",
      "args": [
        "-y",
        "n2c-mcp"
      ],
      "env": {
        "N2C_API_KEY": "your-value",
        "N2C_MCP_ENDPOINT": "your-value"
      }
    }
  }
}

Run this in your terminal

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

Or run it on your computer

claude mcp add nodes2cloud --env N2C_API_KEY=your-value --env N2C_MCP_ENDPOINT=your-value -- npx -y n2c-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "nodes2cloud": {
      "command": "npx",
      "args": [
        "-y",
        "n2c-mcp"
      ],
      "env": {
        "N2C_API_KEY": "your-value",
        "N2C_MCP_ENDPOINT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "nodes2cloud": {
      "type": "http",
      "url": "https://api.nodes2cloud.com/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "nodes2cloud": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "n2c-mcp"
      ],
      "env": {
        "N2C_API_KEY": "your-value",
        "N2C_MCP_ENDPOINT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://api.nodes2cloud.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

N2C_API_KEY secret env
Nodes2Cloud Personal Access Token (n2c_pat_…). Without it the server only lists its tools.
N2C_MCP_ENDPOINT env
Remote MCP endpoint. Defaults to https://api.nodes2cloud.com/mcp.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain nodes2cloud.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

More stars than 0% of the other 1385 servers in this category
Published to the registry more recently than 77% of the other 1385 servers in this category
Basic checks equal to or better than 100% of the other 1385 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Nodes2Cloud safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: N2C_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.2.0) reached the registry 13 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Nodes2Cloud MCP server

Nodes2Cloud lets coding agents (Claude Code, Cursor, VS Code, Windsurf, Zed and other MCP clients) build automation workflows, validate them, and deploy them as Cloudflare Workers in your own Cloudflare account. The server recompiles every deploy itself, and by default each agent deploy waits for you to approve it in the browser.

This package, n2c-mcp, is the stdio entry point: a small local process that forwards MCP messages over HTTPS to the hosted server. It has no runtime dependencies. If your client supports remote MCP servers, you don't need it at all.

Remote endpoint: https://api.nodes2cloud.com/mcp (Streamable HTTP, OAuth 2.1)
Docs: https://docs.nodes2cloud.com/docs/getting-started/mcp
Public tool list: https://api.nodes2cloud.com/.well-known/mcp/server-card.json

Connect

Recommended: remote server with OAuth

No token to copy. The first connection opens a consent screen in your browser that lists what the agent may do.

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

Cursor (.cursor/mcp.json) and Claude Desktop:

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

VS Code (.vscode/mcp.json):

{ "servers": { "nodes2cloud": { "type": "http", "url": "https://api.nodes2cloud.com/mcp" } } }

The installer

npx -y n2c-mcp@latest install                    # pick a client from a menu

npx -y n2c-mcp@latest install --client kiro # or name it npx -y n2c-mcp@latest install --list # every client id

For clients that can sign in through the browser (Kiro, Cursor, VS Code, Antigravity, Zed, Codex, OpenCode and more), the installer writes the remote server's URL into the client's config file and asks for no token: approve the sign-in when the client connects. Pass --key to use a Personal Access Token instead. Clients that are set up with their own command (Claude Code, Devin, Gemini CLI…) or in an app's settings (Claude, ChatGPT…) get their exact steps printed instead.

Flag	Meaning
`--client`, `-c`	Client id or alias, e.g. `kiro`, `cursor`, `vscode`, `codex`, `claude-code`. See `--list`. The numbers 1–11 from earlier versions still work.
`--list`	List the client ids, and which ones get a config file written vs. printed steps
`--key`, `--token`	Personal Access Token. Falls back to `N2C_API_KEY`. Without one, clients that support OAuth sign in through the browser.
`--env`	`production` (default), `staging` or `local`
`--endpoint`	A custom MCP endpoint URL
`--scope`	`user` or `project`: which config file to write. Default: the user file if the client has one, else the project's.
`--print`, `--dry-run`	Print the setup steps without writing any file

The installer merges into an existing config file and keeps your other servers. When it writes a token, the file is restricted to your user.

stdio clients and CI: this package with a Personal Access Token

In Nodes2Cloud, open Integrations → MCP server → Headless & CI Tokens and create a token (n2c_pat_…). It is shown once.
Run the installer with the token, e.g. npx -y n2c-mcp@latest install --client claude --key for Claude Desktop (its config file only runs local servers), or configure a client by hand:

"mcpServers": { "nodes2cloud": { "command": "npx", "args": ["-y", "n2c-mcp"], "env": { "N2C_API_KEY": " " } } } }

With --key, the installer writes the token into the client's config file in plain text and restricts the file to your user. Keep that file out of version control, and revoke the token from the same screen when you no longer need it. --client 11 prints the generic stdio entry above with your token filled in.

Environment

Variable
`N2C_API_KEY`	Personal Access Token. Without it, the server runs in preview mode: it lists its tools, prompts and resource templates from the public server card, and every tool call returns setup instructions instead of doing anything.
`N2C_MCP_ENDPOINT`	Remote endpoint. Default `https://api.nodes2cloud.com/mcp`.

npx -y n2c-mcp --help and --version are also available.

What an agent can do

The server provides 28 tools, plus one tool per workflow you deploy with an MCP Tool trigger:

Author: search the node catalogue and read exact node schemas; create, update, validate (optionally returning the compiled Worker code) and archive workflows.
Set up: check what a deploy still needs, send you one link to connect missing services (agents never handle your secrets), and verify a saved connection.
Deploy: deploy, list versions, read any version's graph, and roll back. Each deploy is recompiled on the server from the saved graph.
Run and observe: run a deployed workflow; list and inspect runs; pause, resume, terminate or send an event to a durable run; read deployment status (telemetry, Cloudflare's own invocation counts, drift) and logs.
Use your workflows as tools: call any workflow you deployed with an MCP Tool trigger.

The full list, with every argument schema, is in the docs and the server card.

Security

No deploy bypass. Agents can only send workflow graph JSON. Every deploy recompiles that saved graph on the server, exactly like the editor's Deploy button.
Approval by default. Unless you choose otherwise on the Connected agents screen, each agent deploy waits for you to approve it in an open Nodes2Cloud tab. You can also turn deploys off for a connection, limit it to specific workflows, and set daily limits.
Scoped access. OAuth connections get only the permissions you approve. A Personal Access Token carries your account's default agent policy.
Secrets stay put. Credentials are encrypted at rest and deployed as Worker secrets in your Cloudflare account. No tool returns a secret.
This package forwards messages and nothing else. It sends your token only to the endpoint you configure (HTTPS by default) and never writes to disk, except when you run install.

Report a vulnerability to security@nodes2cloud.com. See SECURITY.md where available.

Privacy Policy

The full policy is at https://nodes2cloud.com/privacy. In short, for this MCP server:

Data collected. Your account identity, the workflow graphs and names agents create, and which tool was called, when, how long it took, its result code and the client's self-reported name. Tool arguments and results are not logged.
Use and storage. Workflow graphs and versions are stored to provide the service. Run data and logs from your deployed workflows stay in your Cloudflare account and are read on demand, not stored by Nodes2Cloud.
Third-party sharing. Deployed workflows call the services you connect, using your credentials, from your Cloudflare account. Nodes2Cloud's sub-processors are listed at https://nodes2cloud.com/sub-processors.
Retention. Account data is kept while your account is active and deleted when you delete the account, as described in the policy.
Contact. privacy@nodes2cloud.com.

This package itself collects nothing. It sends a User-Agent of n2c-mcp/ with each request.

Support

support@nodes2cloud.com · Issues

License

Apache License 2.0

Nodes2Cloud

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Nodes2Cloud MCP server

Connect

Recommended: remote server with OAuth

The installer

stdio clients and CI: this package with a Personal Access Token

Environment

What an agent can do

Security

Privacy Policy

Support

License