Index / MCP servers / Flux Cloud

Flux Cloud MCP server

Flux Cloud is an MCP server with 15 tools an agent can call, among them flux_build_spec, flux_cancel_app, flux_control_app. It answers at https://mcp.runonflux.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 5 of 5 times since 12 September 2026; the last check, on 18 October 2026, succeeded.

Status
Answering
Tools
15
Reliability
5 of 5 checks
Response time
202 ms
Transport
streamable HTTP
Last checked
18 October 2026

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

Description as the publisher wrote it.

The 15 tools Flux Cloud offers

ToolWhat it does
flux_build_specTurns 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.
Inputs: name, description, components, instances, months, expireBlocks
flux_cancel_appEnds 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.
Inputs: name, confirm, fluxIdPrivateKey, paymentPrivateKey
flux_control_apprestart: 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
Inputs: name, action, scope, nodeIp, hard, fluxIdPrivateKey
flux_deploy_appValidates 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 spen
Inputs: spec, enterprise, confirm, fluxIdPrivateKey, paymentPrivateKey
flux_generate_keysCreates 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, th
Inputs: fluxIdPrivateKey, paymentPrivateKey
flux_get_appLooks up any app on the network by name and returns its published specification, expiry, running instances and URLs.
Inputs: name, fluxIdPrivateKey, paymentPrivateKey
flux_get_app_logsFetches the last N log lines of an app (or one component of it) from one of the nodes running it. Requires the owner key.
Inputs: name, component, lines, nodeIp, fluxIdPrivateKey, paymentPrivateKey
flux_get_app_statsCPU, memory and network stats of the containers of an app on one node. Requires the owner key.
Inputs: name, component, nodeIp, fluxIdPrivateKey, paymentPrivateKey
flux_get_identityReturns 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.
Inputs: fluxIdPrivateKey, paymentPrivateKey
flux_get_network_infoNode counts by tier, current block height, FLUX/USD rate and the deployment payment address.
Inputs: fluxIdPrivateKey, paymentPrivateKey
flux_get_pricingReturns 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.
Inputs: fluxIdPrivateKey, paymentPrivateKey
flux_list_my_appsLists every app registered by the owner (or a given Flux ID) with expiry and instance counts.
Inputs: owner, nameContains, fluxIdPrivateKey, paymentPrivateKey
flux_quote_appReturns 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.
Inputs: spec, fluxIdPrivateKey, paymentPrivateKey
flux_validate_specRuns 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.
Inputs: spec, network, fluxIdPrivateKey, paymentPrivateKey
flux_wait_for_appPolls 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=tr
Inputs: name, txid, previousHash, timeoutSeconds, fluxIdPrivateKey, paymentPrivateKey

Add Flux Cloud to your AI client

Every block below points at https://mcp.runonflux.com/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http flux-cloud https://mcp.runonflux.com/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "flux-cloud": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.runonflux.com/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "flux-cloud": {
      "url": "https://mcp.runonflux.com/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "flux-cloud": {
      "type": "http",
      "url": "https://mcp.runonflux.com/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "flux-cloud": {
      "url": "https://mcp.runonflux.com/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "flux-cloud": {
      "serverUrl": "https://mcp.runonflux.com/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "flux-cloud": {
      "url": "https://mcp.runonflux.com/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Flux Cloud
version: 0.0.1
schema: v1
mcpServers:
  - name: Flux Cloud
    type: streamable-http
    url: https://mcp.runonflux.com/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "flux-cloud": {
      "httpUrl": "https://mcp.runonflux.com/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "flux-cloud": {
      "type": "http",
      "url": "https://mcp.runonflux.com/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "flux-cloud": {
      "url": "https://mcp.runonflux.com/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.runonflux.com%2Fmcp&type=streamable_http&id=flux-cloud&name=Flux%20Cloud

Is Flux Cloud up right now?

It answered our last check on 18 October 2026 in 202 ms. Over 5 checks since 12 September 2026 it answered 5. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Flux Cloud

Questions about Flux Cloud

How many tools does Flux Cloud have?

15, as returned by the server's own tools/list on 24 September 2026: flux_build_spec, flux_cancel_app, flux_control_app, flux_deploy_app, flux_generate_keys, flux_get_app, flux_get_app_logs, flux_get_app_stats, and 7 more.

Is Flux Cloud down?

It answered our last check on 18 October 2026 in 202 ms. Over 5 checks since 12 September 2026 it answered 5.

How do I add Flux Cloud to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.runonflux.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Flux Cloud need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.runonflux. Endpoint host: mcp.runonflux.com. ARD identifier: urn:air:io.github.runonflux:mcp:flux-cloud-mcp. First indexed 12 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.