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.

Start free
Free plan includes MCP · No credit card · Works on Cloudflare's free plan
drag to spin
Demo

Watch an agent build one.

claude code · mcp

>

  • list_node_types246 nodes · 18 groups
  • get_node_schemas5 types
  • create_workflowrefund_approval
  • update_workflow7 nodes · 6 edges
  • validate_workflowok · 0 errors · 16.5 KB gzip

The agent writes graph JSON, never a script. What it hands us is data, which is the only reason the next three steps are possible at all.

Refund approval0/7 nodes
truefalsetrue01MCP Toolmcp_trigger02If/Conditionif03Slack: Post MessageslackReached on the "true" branch04Wait for Eventwait_for_eventdurable05If/Conditionif06HTTP Requesthttp_requestReached on the "true" branch07HTTP Requesthttp_requestReached on the "false" branch
Asks before deploying
by default
Can bypass the compiler
no
Runs on
your account
Available on
every plan
How it works

From canvas to cloud in minutes.

↺ Agent Tool CallTriggerrefund_callMCP Agent inputReview Gatepolicy_checkAST & schemaWorkerstripe_refundCloudflare edge
  1. Step 01 (Author): Your agent writes the workflow over MCP, or you build it on the canvas or describe it in plain English.
  2. Step 02 (Review): A structural validator checks the graph, then our server recompiles it to reviewable TypeScript.
  3. Step 03 (Deploy): You approve the changes, and the Worker deploys into your Cloudflare account.
  4. Step 04 (Call back): The Worker runs in your account, and your agent can call it as a tool.
01Author
02Review
03Deploy
04Call back
AuthorSTEP 01 OF 04

Your agent writes the workflow over MCP, or you build it on the canvas or describe it in plain English.

Integrations

Yes, it connects to that.

SlackOpenAIStripeGitHubNotionAirtableHubSpotSupabaseGoogle SheetsAnthropicAnd more

Pre-wired for the modern stack.

What you build

Infrastructure-grade workflows.

Our analyzer reads your graph's shape and automatically assigns the correct Cloudflare compile target under the hood.

Refunds a human has to approve

Human in the loop
compiles to Cloudflare Workflow

A support agent that files its own tickets

AI agent
compiles to Email Worker

The 9am revenue digest

compiles to Scheduled Worker

Ask your docs, in chat

RAG
compiles to Worker

Form to CRM, without the copy-paste

compiles to Worker

Nightly sync into the warehouse

compiles to Cloudflare Workflow

GitHub issue triage & auto-reviewer

DevOps
compiles to Worker

Instant payment webhook & ledger sync

compiles to Cloudflare Workflow

Auto-scheduler & calendar invite agent

compiles to Email Worker
Control

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.

Read the full security model →
Cost

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.

Monthly cost · both axes logarithmic100,000 runs
YouA leading per-task platformHover or drag the chart

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.

Against a per-task platform

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
Start freeFree plan includes 10 workflows · No credit card
Questions

The questions you were going to ask anyway.

Yes. Run: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.

No. Describe what you need in plain English and the assistant creates the steps for you to review, or build by dragging nodes on the canvas. Nothing goes live until you approve it. The one thing you set up yourself is a free Cloudflare account, connected once.

You need an account, not expertise. Your Workers run in your own Cloudflare account (the free plan works), and Nodes2Cloud provisions the databases, storage buckets, queues, and secrets they need for you.

No. Cloudflare's free tier includes 100,000 Worker requests per day, D1 databases, and Workflows. If your volume expands, you pay Cloudflare directly and we add nothing per run.

Yes. Add an MCP Tooltrigger to your workflow. The deployed Worker exposes an MCP endpoint that coding agents can discover and call directly using a bearer token you control. If the workflow has a wait, a delay or an approval step, the call returns the run's id and the fact that it started, not its result, because a durable run can park for days.

246 nodes are supported out of the box, connecting to 158 external services. You can also connect to any REST API using the HTTP Request node or run custom JavaScript via the Code node.

Not in production. Deployed workflows run in your Cloudflare account, so their payloads go straight between your Worker and your services. Test runs, live debug sessions and agent tool calls made through our MCP server pass through us in transit; none of it is stored. Your API keys are encrypted under a key derived for your account, and the master key lives in Cloudflare's secret store, never in our database.

Your automations continue running uninterrupted because they live in your Cloudflare account. You can also export your project as standard TypeScript source code and deploy it from your own CI pipeline at any time.

Not today. We plan to release the compiler and node libraries under Apache-2.0 in the future, but Nodes2Cloud is currently proprietary.
free plan · MCP included

Ship your first automation in minutes.You approve what goes live.

Start free
Free plan · 50 AI credits a month·No credit card required·Install via MCP for your coding agent
early access

Join the waitlist

We’re opening Nodes2Cloudin batches. Leave your details and we’ll email you when it’s your turn.

We’ll only use this to contact you about access. See our privacy policy.