An MCP server that connects to Vercel API
Nothing to run from here
Nodes2Cloud is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
24
downloads a day
local
or remote
558
downloads in 30d
What it does
Build, validate and deploy workflows as Cloudflare Workers in your own account, with approval.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user nodes2cloud-mcp '--' npx -y n2c-mcp
# 2 — ask your agent for something these tools do
# list_workflows, get_workflow, create_workflow and 30 more
Remote: OAuth sign-in · Package: no sign-in.
Nodes2Cloud costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NOAll 1 server
nodes2cloud1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user nodes2cloud-mcp '--' npx -y n2c-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://api.nodes2cloud.com/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http nodes2cloud-mcp https://api.nodes2cloud.com/mcpFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take N2C_API_KEY (Nodes2Cloud Personal Access Token (n2c_pat_…). Without it the server only lists its tools.), N2C_MCP_ENDPOINT (Remote MCP endpoint. Defaults to https://api.nodes2cloud.com/mcp.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
33 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List the workflows this connection can access, personal and shared through a workspace, most recently updated first. Each entry has its id, name, status and live URL if deployed. Start here to find a workflowId. If the owner restricted this connection to certain workflows, only those are listed…
No parameter schema on file.
Get one workflow's editable graph (nodes, edges, settings) and metadata, including the updatedAt value update_workflow requires. Pass versionNumber to instead get that deployed version's frozen graph together with the version before it (previousVersion, null for version 1), so you can see…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| versionNumber | integer | no | A saved version to read instead of the current draft. Omit for the draft. |
Create a new, undeployed workflow, optionally with an initial graph. Look up node types with list_node_types and get_node_schemas first rather than guessing property names. Returns the saved workflow, including its id and updatedAt. Nothing runs or deploys until deploy_workflow. Refused when the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Human-readable workflow name. |
| nodes | array | no | Initial nodes. Omit to start empty. |
| edges | array | no | Initial edges between those nodes. |
Replace a workflow's saved draft: any of name, nodes and edges you pass overwrite the stored ones whole (send the complete node and edge lists, not a patch). Requires the updatedAt from your last get_workflow or create_workflow; if someone edited it since, this returns conflict and changes…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| name | string | no | New name. Omit to keep it. |
| nodes | array | no | The complete new node list. Omit to keep the current nodes. |
| edges | array | no | The complete new edge list. Omit to keep the current edges. |
| updatedAt | string | yes | The workflow's updatedAt exactly as last returned to you. |
Compile a workflow without deploying it and report every error, each with the node it concerns. Use it after every edit and before deploy_workflow. Checks the saved graph by workflowId, or an unsaved graph passed as nodes and edges (given with a workflowId, they replace the saved ones for this…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | no | The workflow's id, from list_workflows or create_workflow. |
| nodes | array | no | Nodes to check instead of the saved ones. Pass with edges. |
| edges | array | no | Edges to check instead of the saved ones. Pass with nodes. |
| includeCode | boolean | no | Also return the compiled script and metadata when valid. Default false, to save tokens. |
Deploy a saved workflow to the user's own Cloudflare account, replacing any live version. The server recompiles the saved graph itself; no code you send is ever deployed. Save and validate first, and call check_setup early so missing connections are fixed in time. Unless the owner allowed this…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| requestState | string | no | Only on a retry: the opaque requestState from a previous input_required answer to this same call. Never invent or edit one. |
Archive a workflow: it leaves the active list and can no longer be edited or deployed until the owner restores it in the Nodes2Cloud editor. Nothing is permanently deleted, and a version already deployed keeps running in the user's Cloudflare account. Only use this when the user asks to remove a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
List the services the user has connected (Slack, Google, Stripe and so on), with each connection's id, provider, name, kind and status. Metadata only: no secret or token is ever returned. Put a connection's id in a node's credential field when building a workflow. To see only what one workflow…
No parameter schema on file.
Search the catalogue of node types a workflow can use: triggers (webhook, schedule, email, agent tool), logic (if, switch, loop, wait, code) and integrations with third-party services. Returns each type's id, display name, description, category and group, without property schemas to keep it small.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Case-insensitive substring matched against the type id and display name, e.g. 'slack'. |
Get the full property schema of one or more node types: every property's key, type, options, default and whether it is required, plus input and output ports. Use it before writing a node's data so property names are exact rather than guessed. An unknown type comes back with an error entry…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| types | array | yes | Exact type ids from list_node_types, e.g. ['webhook_trigger', 'if']. |
Run one saved node on its own, for real, to check its configuration and connection, the way the editor's test button does. It makes the node's actual call to the third-party service, so a 'send' node really sends. With no upstream run, {{ … }} expressions are passed through as literal text; the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| nodeId | string | yes | The node's id within the saved graph. |
Check whether the user can deploy right now and what is missing: whether Cloudflare is connected (including the one-time workers.dev subdomain step, which otherwise only fails after a deploy) and, given a workflowId, which services its nodes need that are not connected yet (missingProviders).…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | no | Also report which services this workflow still needs connected. |
| sessionId | string | no | A sessionId from request_connections, to poll that request's progress. |
Create one short link the user opens to connect the services you name, with one button per service. Use the ids from check_setup's missingProviders, plus cloudflare if it is not connected. You cannot create a connection yourself, and must never ask the user to paste a secret into the chat:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| providers | array | yes | Provider ids, e.g. ["google_gmail","slack","cloudflare"]. |
| workflowId | string | no | The workflow this is for, if any. |
Run a deployed workflow once, for real, with an optional JSON payload as its trigger input, and return what happened. A simple workflow answers with its HTTP status, duration and response body. A durable one (with a wait, delay, approval or sub-workflow) starts a run and returns its instanceId and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| payload | object | no | JSON trigger input, as a webhook body would carry it. Defaults to {}. |
| via | string | no | auto (default) calls the live trigger, or starts a durable run when the trigger's secret cannot be reproduced. instance always starts a durable run (durable workflows only). |
| instanceId | string | no | Your own id for a durable run, so you can poll it with get_run. Implies via instance. Cannot start with 'cf_'. |
List a deployed workflow's recent runs, newest first, read on demand from the user's own Cloudflare account. source: history (default) lists completed runs with an executionId, status and duration from the workflow's run log; it is empty until something has actually run. source: instances…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| source | string | no | history (default): the run log. instances: durable runs and their state. |
| status | string | no | Only with source instances: return runs in this state. |
| order | string | no | Only with source history. Default newest; oldest pages through all retained history. |
| limit | integer | no | Runs per page, 1-100. Default 20. |
| cursor | string | no | The cursor from the previous page, with the same source and order. |
Get one run's details. Pass executionId (from list_runs source history) for step-by-step status, durations and recorded inputs and outputs. Pass instanceId (from run_workflow or list_runs source instances) for a durable run's state, step history, output and error, plus awaitingEvents: the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| executionId | string | no | A run-log id from list_runs (source history). |
| instanceId | string | no | A durable run's id from run_workflow or list_runs (source instances). |
| simple | boolean | no | With instanceId only: skip step detail and return status and stepCount. |
Act on one in-flight durable run: pause, resume, terminate (stops it where it is; completed steps are not undone), or send_event to deliver an event to a run parked on a wait or approval, resuming it. For send_event, read get_run first and use one of its awaitingEvents as eventType:…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| instanceId | string | yes | The durable run's id. |
| action | string | yes | — |
| eventType | string | no | Required for send_event: one of the run's awaitingEvents, exactly. |
| payload | object | no | send_event only: JSON delivered to the waiting node. |
Answer 'is this deployed workflow healthy, and is it still what we deployed?' in one call. stats: run counts, error rates and p50/p95 durations per node type from the workflow's own telemetry. health: Cloudflare's independent count of invocations, errors and CPU time, which also catches…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| since | string | no | Time window for stats and health. Default 24h. |
| include | array | no | Sections to read. Default all three; fewer is faster. |
Read the raw log lines and uncaught exceptions a deployed workflow produced in the user's Cloudflare account, newest first. Use it when a run failed without explanation, or get_deployment_status shows errors you need to see. source in the answer says which log store responded; null means neither…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| since | string | no | Time window. Default 24h. |
| limit | integer | no | Lines to return, 1-100. Default 50. |
| source | string | no | Force one store: Cloudflare Workers Logs, or the workflow's own log forwarder. Default tries the first, then the second. |
List one workflow's deployed versions, newest first, marking which one is live now. Every deploy creates a version. Use the version numbers with get_workflow (to read or compare a version's graph) and rollback_workflow (to make an earlier one live again).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
Make an earlier deployed version of a workflow live again in the user's Cloudflare account, replacing what is running now. Get version numbers from list_workflow_versions. Only do this when the user asks. Refused if the owner turned off deploys for this connection. For a durable workflow, the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| versionNumber | integer | yes | The version to make live, from list_workflow_versions. |
| restoreDraft | boolean | no | Also replace the editable draft with this version's graph. Default false. |
List the files a deployed workflow's runs have stored in its own storage bucket in the user's Cloudflare account, with each file's key, size and last-modified time. readPath is the URL template that downloads one file. A workflow that never stored a file returns an empty list, not an error. Pass…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| limit | integer | no | Files per page, 1-1000. Default 100. |
| cursor | string | no | The cursor from the previous page. |
Check a saved connection against its provider right now (a read-only identity call) and record the result. Use it when a node fails with what looks like an authentication error: access that worked when it was saved may since have been revoked or narrowed. Returns the connection's metadata with its…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| credentialId | string | yes | The connection's id, from list_connections or check_setup. |
Generate a new secret for a deployed workflow's webhook trigger, redeploy it, and return the new secret. This immediately breaks anything still calling the webhook with the old secret, so only do it when the user asks or needs the secret to call the webhook themselves. The new secret takes a few…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
Read the user's plan and its limits: how many workflows may be saved and live at once, how many deployed workflows can be offered to agents as tools, and which features are included. Also lists each shared workspace's own limits, since a workflow's limits come from its owner's plan. Check this…
No parameter schema on file.
Ask a connected service which values really exist, such as a spreadsheet's tab names, an Airtable base's tables and typed fields, a Typeform's questions or a Google account's calendars. Use it while configuring a node instead of guessing a name: a guessed tab or field deploys fine and only fails…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflowId | string | yes | The workflow's id, from list_workflows or create_workflow. |
| loader | string | yes | Which picker to run. |
| credentialId | string | yes | A credential for the loader's provider — check_setup reports what is connected. |
| params | object | no | Loader-specific selectors, e.g. { spreadsheetId }, { baseId, tableId }, { sobject }. |
Call one of the user's deployed agent-tool workflows (those with an MCP Tool trigger) by its tool name or workflow id, with the arguments its schema declares. Use it when the workflow is not in your tool list: one deployed since you connected only appears there after you reconnect, but is callable…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The tool name from the workflow's MCP Tool trigger, or the workflow id. |
| arguments | object | no | Arguments matching that tool's schema, from list_deployed_tools. |
List the user's deployed workflows that agents can call as tools right now (those deployed with an MCP Tool trigger), each with its tool name, description and argument schema. Use it to find a workflow deployed after you connected, then call it with call_deployed_workflow. If the plan's limit…
No parameter schema on file.
Receive a webhook and post a formatted message to a Slack channel.
No parameter schema on file.
On a schedule, fetch data from an API and email or post a summary.
No parameter schema on file.
When an email arrives, extract fields and append a row to Google Sheets.
No parameter schema on file.
Build a workflow exposed as an MCP tool, so you can call it yourself afterwards.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Nodes2Cloud or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 1.2.0 · scanned 28 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest926396f28c4264425660b196d020c7d71c2d13bc520d6bdaa1028ea7e352b64f
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest926396f28c426442
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.2.0. Pin a release below and the command asks for exactly that one.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Nodes2Cloud can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.