Flux Cloud MCP Server

by runonflux Your server? Claim it

answering

Flux Cloud is answering right now. Last checked 2 min ago. 1 626 installs a week from npm. It exposes 15 tools. Last commit 13 Sep 2026.

Deploy, pay for and manage apps on Flux Cloud, the decentralized cloud. Prices in USD.

Installs per day peak 522 · avg 56

a month agotoday

Uptime history 6 days of history · worst day 92%

6 days agonow

96.7%

Uptime 24h

89 of 92 checks

Tools

read from the server

405 ms

Response time

average over 24h

1 626

Installs / week

npm and PyPI

Flux Cloud does not always answer

Over the last week it answered 97.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add flux-cloud-mcp --transport http https://mcp.runonflux.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "flux-cloud-mcp": {
      "url": "https://mcp.runonflux.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.flux-cloud-mcp]
url = "https://mcp.runonflux.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "flux-cloud-mcp": {
      "url": "https://mcp.runonflux.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "flux-cloud-mcp": {
      "url": "https://mcp.runonflux.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: FLUX_ID_PRIVATE_KEY (WIF private key of the Flux ID that owns your apps. Optional; read-only tools work without it. flux_generate_keys creates one.), FLUX_PAYMENT_PRIVATE_KEY (WIF private key of the Flux address that pays deployment fees. Optional; fund it with only what you intend to spend.). The author declared them in the registry entry; get the values from the project itself.

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

flux

flux_build_spec

Turns images, ports, resources and a term into a complete, correctly formatted v8 specification, with public ports auto-picked and data replication enabled. Returns the spec plus local validation errors and warnings.

flux_cancel_app

Ends an app early by updating its term so it expires within about an hour. The network then uninstalls it everywhere. With confirm=true this signs and pays the (usually minimal) update; without it, returns the plan.

flux_control_app

restart: restarts containers. redeploy: pulls the image again and recreates containers (hard=true also wipes data). remove: uninstalls from nodes; the registration stays and the network re-spawns it elsewhere, so use flux_cancel_app to stop paying. Scope is one node (nodeIp) or every node running the app (global). Requires the owner key.

flux_deploy_app

Validates the specification on a node, quotes it, and with confirm=true signs it with the Flux ID, broadcasts it and pays the quoted FLUX from the payment address. Without confirm it only returns the plan (price, balance, warnings) and spends nothing. Registers a new name or updates an existing app of the same owner. Then call flux_wait_for_app with the returned txid.

flux_generate_keys

Creates two fresh private keys (WIF): one for the Flux ID that will own apps, one for the address that pays. The response contains the secrets; store them in the MCP server environment as FLUX_ID_PRIVATE_KEY and FLUX_PAYMENT_PRIVATE_KEY, then restart the server. Nothing is stored or sent anywhere by this tool.

flux_get_app

Looks up any app on the network by name and returns its published specification, expiry, running instances and URLs.

flux_get_app_logs

Fetches the last N log lines of an app (or one component of it) from one of the nodes running it. Requires the owner key.

flux_get_app_stats

CPU, memory and network stats of the containers of an app on one node. Requires the owner key.

flux_get_identity

Returns the Flux ID (app owner address), the payment address and its spendable FLUX balance with its USD value. Explains what to configure if keys are missing. Never returns private keys.

flux_get_network_info

Node counts by tier, current block height, FLUX/USD rate and the deployment payment address.

flux_get_pricing

Returns the current USD rate card, the live FLUX/USD rate, the pay-in-FLUX discount and instant USD estimates for a few reference sizes. Use flux_quote_app for the exact price of a specific app.

flux_list_my_apps

Lists every app registered by the owner (or a given Flux ID) with expiry and instance counts.

flux_quote_app

Returns the Flux Cloud price for registering the given specification, or for updating it if an app of that name already exists (the unused part of the current term is credited). Price is in USD with the FLUX amount at market rate.

flux_validate_spec

Runs the local rule checks, then asks a FluxOS node to verify the specification exactly as it would at registration (image reachable, architecture, ports, name availability). Returns the node-formatted spec on success.

flux_wait_for_app

Polls the network for up to timeoutSeconds (default 45 to fit hosts with a 60 s tool timeout, max 600). Returns payment confirmations, whether the spec was accepted, and the running instances with URLs. Safe to call repeatedly until done=true.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.runonflux.com/mcp	streamable-http	answering	483 ms	2 min ago

Alternatives to Flux Cloud

same job, measured the same way

Deploy

by nometria

Deploy any app to any cloud. 20 tools for deployments, previews, and management.

45 installs/wk local only

AppCrane

by gitayg

Deploy and manage apps on your own AppCrane instance, the self-hosted PaaS for AI-built apps.

391 installs/wk local only

clawops

by dfridkin

Deploy and manage self-hosted OpenClaw instances across clouds

625 installs/wk local only

Bult

by bultcloud

Deploy and manage Bult apps from AI coding agents.

26 installs/wk local only

Qovery MCP Server

by qovery

Deploy and manage your apps on Qovery

answering

Agentmark AI

by agentmark-ai

Inspect AgentMark traces and drive AgentMark Cloud: apps, experiments, metrics, deployments.

47 installs/wk local only

InstaPods

by instapods

Deploy and manage web apps on InstaPods: create pods, push files, run commands, read logs.

answering

Devopness

by devopness-mcp

Devopness MCP server for DevOps happiness! Empower AI Agents to deploy apps and infra, to any cloud.

answering

Flux Cloud — questions

Answers built from our own checks of this server.

What can Flux Cloud do?

It exposes 15 tools, read directly from the server on our last check. Among them: flux_build_spec, flux_cancel_app, flux_control_app, flux_deploy_app, flux_generate_keys, flux_get_app and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Flux Cloud working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 92 checks got a reply (96.7%), average response time 405 ms. The bar chart above shows every period we have measured.

How do I connect Flux Cloud?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Flux Cloud need an API key?

No. Flux Cloud completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Flux Cloud?

It answers our handshake in 405 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Flux Cloud?

The npm package @runonflux/flux-cloud-mcp was installed 1 626 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Flux Cloud open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.