Deploy From Your AI Agent: The Flux Cloud MCP Server
Fluxers! “Deploy on Flux” is now something an AI agent can do by itself. The Flux Cloud MCP server is live, published to npm and to the MCP Registry, and it works with Claude Code, Claude Desktop, Cursor, Windsurf, OpenCode and every other MCP host.
This was on the Q4 2026 roadmap. It shipped in September.
What it does
MCP — the Model Context Protocol — is how an AI agent is given tools it can call. The Flux Cloud MCP server gives an agent the whole lifecycle of an application on the decentralized cloud: quote it in US dollars, deploy it, pay for it, watch it come up, read its logs, update it, and cancel it.
So instead of you reading a deployment guide, your agent reads the tool schema. You describe what you want running, it sizes it, quotes it, asks you to confirm, and deploys.
There is no account
This is the part that matters, and it is the reason Flux can do this and a centralised cloud cannot. There is no sign-up, no email, no dashboard to register in. Two keys are the whole identity.
- The Flux ID key (address starts with 1) owns apps. It signs specifications and API sessions, and it never holds funds.
- The payment key (address starts with t1) holds FLUX and pays deployment fees on-chain.
The server will generate a pair for you with its flux_generate_keys tool. Fund the payment address with FLUX, and you can deploy. Keys are optional, too — without them every read-only tool still works, so an agent can explore the network and price things up before anyone has spent anything.
This is the practical form of a principle in the new Flux whitepaper: a program can hold a key, but it cannot hold a corporate account. Paying on Flux is a signed transaction, not a billing relationship, which is why the caller does not have to be a person.
Honest pricing
Every price the server shows is the Flux Cloud USD price — the same one home.runonflux.io charges — converted to FLUX at the live market rate, with the 5% pay-in-FLUX discount applied.
Quotes come from the network itself, so they already include the $0.99 minimum, hardware and term discounts, and update credits. The blockchain’s own acceptance threshold is several times lower than that, and the server never shows it as a price; it is only checked as a guard before a payment is broadcast. An agent quoting you a number that is not the number you would have paid in the UI would be a bug, not a feature.
Installing it
Global install:
npm install -g @runonflux/flux-cloud-mcp
Or run it without installing at all, with npx @runonflux/flux-cloud-mcp. In Claude Code it is a single command:
claude mcp add flux-cloud -s user -e FLUX_ID_PRIVATE_KEY=<wif> -e FLUX_PAYMENT_PRIVATE_KEY=<wif> -- npx -y @runonflux/flux-cloud-mcp
Claude Desktop, Cursor and Windsurf take the same thing as a JSON block in their config. OpenCode has its own equivalent. All of it is in the repository README.
Hosted, if you would rather not run it
Version 0.2.0 added a hosted Streamable HTTP mode with per-call keys, so you can point a host at mcp.runonflux.io instead of running the server locally. The image is published to GHCR, and the deploy spec is in the repository — which means the hosted MCP server is itself a Flux app.
It tells you why something is down
A lot of the work since the first release has gone into diagnostics, because “my app is not responding” is the question an agent is worst at answering on its own. flux_get_app now distinguishes between an app with no listener, a non-HTTP service, and a private app — three situations that look identical from outside and have completely different fixes.
It also queries the responsible gateway node directly, so when a gateway is having a bad day, the diagnosis names the gateway instead of blaming your container. And private apps are discovered through the owner-authenticated decrypted specification, so an encrypted enterprise deployment is reported as what it is rather than as an app with no parts.
Try it
Point your agent at it and ask for something. “What would a Minecraft server for twenty players cost on Flux for three months?” is a good first question, because it exercises sizing, the live FLUX rate and the term discount, and it costs nothing to ask. The package is @runonflux/flux-cloud-mcp, and the documentation lives on the Flux docs site under Deploy with AI Agents.
Posted in Product Updates
by RunonFlux
Tags:
Comments
Leave a Reply
You must be logged in to post a comment.
