com.nodes2cloud/mcp is an MCP server that build, validate and deploy workflows as Cloudflare Workers in your own account, with approval. Its tool list has not been published yet over http and stdio, requires no API key, and scores 60/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"nodes2cloud": {
"url": "https://api.nodes2cloud.com/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Build, validate and deploy workflows as Cloudflare Workers in your own account, with approval.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked n2c-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in cloud / devops
MCP server for using the GitLab API
Cloud-powered AI platform with multi-agent swarms, sandboxes, and workflow automation
Gives AI development tools Firebase-specific capabilities and expertise.
MCP server for discovering, reading, and changing ZenML resources with compact generic tools
MCP Security Weekly
Get CVE alerts and security updates for com.nodes2cloud/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
https://api.nodes2cloud.com/mcp (Streamable HTTP, OAuth 2.1)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" } } }
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 <PAT> 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, then a prompt that doesn't echo. Prefer those two: a token on the command line stays in your shell history. 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. |
--allow-project-token | Write a token into a project config file that git doesn't ignore. Refused by default, since that file could be committed. |
--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.
In Nodes2Cloud, open Integrations → MCP server → Headless & CI Tokens and create a token (n2c_pat_…). It is shown once.
Run the installer, e.g. npx -y n2c-mcp@latest install --client claude for Claude Desktop (its config file only runs local servers), and paste the token at the prompt (or set N2C_API_KEY first). Or configure a client by hand:
{
"mcpServers": {
"nodes2c