Skip to main content
Glama
Sign In
Flux Cloud MCP server

Flux Cloud MCP server

Official
by RunOnFlux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Flux Cloud MCP server

No user-submitted related servers found.

    Related Servers

    • CloudGPU MCP

      mrhy7176
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to check live GPU prices, get a cost quote, rent a per-minute GPU instance, upload code and data, run jobs in the background, tail logs, download results and destroy the instance to stop billing. Includes guardrail limits on spend, hours and idle time, safe file transfer, and access to an OpenAI-compatible model API for inference without renting a GPU.
      1,341 npm
      MIT
    • Nexlayer MCP

      Nexlayer MCPofficial

      Nexlayer
      F
      license
      Not graded
      quality
      D
      maintenance
      Agentic cloud platform with 45+ MCP tools. Deploy any containerized stack, debug live pods (shell, file editing, DB queries), manage custom domains & TLS, push to built-in container registry, scale pods, and manage GPU workloads. The infrastructure layer where AI agents ship software to production.
      9
      -

    • IMD Kit MCP Server

      RobertKodes
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers and AI agents to check, price, pay for, and follow paid work on a network of AI agents over stdio or streamable HTTP, exposing eight tools where only ordering can spend and only behind four safety gates. Without a wallet key every tool stays free and ordering returns a dry run, so an agent can inspect plans and prices before any payment is signed.
      MIT
    • ComputeNexa MCP Server

      ComputeNexa MCP Serverofficial

      computenexa-gpuInfrastructure
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to browse live GPU stock and prices, then launch, extend or stop private GPU machines — returning a cost quote first and only spending money after the user confirms. Read-only tools cover apps, machines, usage, receipts, projects and endpoints, with per-call spending caps and API keys kept in local settings.
      15
      MIT

    • Theagora MCP Server

      theagoralabs
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to participate in a marketplace for buying, selling, and trading services with atomic escrow and cryptographic verification. It provides 27 tools for discovery, order book management, and automated service delivery with zero gas fees.
      32
      60 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes across the deployment lifecycle, with explicit descriptions separating build/validate/quote/deploy. The main potential confusion is between flux_cancel_app and flux_control_app's remove option, but the descriptions clarify that cancel stops payment while remove only uninstalls from nodes.

    Naming Consistency5/5

    All tool names use the same flux_ prefix and consistent snake_case verb_noun pattern, such as flux_get_app, flux_deploy_app, flux_list_my_apps, and flux_get_app_logs. There are no mixed conventions or ambiguous naming styles.

    Tool Count5/5

    15 tools is well within the appropriate range for a cloud deployment and management server. Each tool covers a distinct step in the Flux app lifecycle, from key generation and pricing to deployment, monitoring, and cancellation.

    Completeness5/5

    The surface covers the full app lifecycle: identity and keys, pricing and quotes, spec building and validation, deployment and waiting, listing and inspection, logs and stats, runtime control, cancellation, and network info. Update is handled through deploy_app for existing apps, so no major gaps are apparent.

    Resources