Let your agent build workflows that ship safely to Cloudflare.
Ask from Claude Code, Cursor or plain English. It compiles to code and goes live in your Cloudflare account once you approve.
Watch an agent build one.
- Asks before deploying
- by default
- Can bypass the compiler
- no
- Runs on
- your account
- Available on
- every plan
From canvas to cloud in minutes.
- Step 01 (Author): Your agent writes the workflow over MCP, or you build it on the canvas or describe it in plain English.
- Step 02 (Review): A structural validator checks the graph, then our server recompiles it to reviewable TypeScript.
- Step 03 (Deploy): You approve the changes, and the Worker deploys into your Cloudflare account.
- Step 04 (Call back): The Worker runs in your account, and your agent can call it as a tool.
Your agent writes the workflow over MCP, or you build it on the canvas or describe it in plain English.
Yes, it connects to that.
Pre-wired for the modern stack.
Infrastructure-grade workflows.
Our analyzer reads your graph's shape and automatically assigns the correct Cloudflare compile target under the hood.
A support agent that files its own tickets
AI agentThe 9am revenue digest
Ask your docs, in chat
RAGForm to CRM, without the copy-paste
Nightly sync into the warehouse
GitHub issue triage & auto-reviewer
DevOpsInstant payment webhook & ledger sync
Auto-scheduler & calendar invite agent
Control over every agent change.
Your agent can build, check, and propose. By default, nothing reaches your Cloudflare account until you say yes. AI is never a deploy bypass.
Your agent never sees a credential
No endpoint returns a credential value to an agent or to you. Test runs send credentials only to that service's own API.
Encrypted for your account alone
AES-256-GCM under a key derived for your account. The master key lives in Cloudflare's secret store, never in our database.
Keys we cannot use
Lock a credential with a passkey or passphrase. We hold nothing that can unwrap it, so deploying requires you to unlock it.
Permissions per agent
Choose what each connected agent can do, which workflows it can touch, and cap its daily actions. An agent never exceeds what you granted at sign-in.
Callable tools need a token
A workflow your agent can call requires a bearer token by default. A blank token will not compile.
We store no execution data
In production, data moves between your Cloudflare account and your services. Test runs, live debug sessions, and agent tool calls pass through us in transit and are stored nowhere.
Scale your automations, not your bill.
A flat subscription that never charges per run. Executions run directly in your Cloudflare account at direct compute rates, not on a metered per-task bill.
The shaded gap is what a per-task platform would have cost instead.
Modeled on standard published per-task tiers for a typical 4-step workflow (W1 workload). Third-party plans and terms may vary; Cloudflare compute is billed directly at cost.
22×
less, at this volume — $500 a month against $23.
- Nodes2Cloud Pro
- $18flat $18/mo · or start on Developer free plan
- Cloudflare requests
- $5billed to your Cloudflare account
- Cloudflare steps · up to 4/run
- $0within free allowance
The questions you were going to ask anyway.
npx -y n2c-mcp@latest installto give Claude Code, Cursor, Codex, Kiro, VS Code, Zed or any other MCP client 28 tools to browse schemas, build workflows, preview compiled Workers, test nodes, and deploy. It works on every plan, including free. Deploys require your approval by default.