Flux MCP Server

RunAPI Flux MCP server for image generation: create tasks, poll results, and check pricing across 3 model variants from Claude Code, Codex, Cursor

Local serverstdio

What is the Flux MCP server?

Flux MCP server exists for a simple reason — assistants are far more useful when they can act on Flux directly instead of describing what you should do. RunAPI Flux MCP server for image generation: create tasks, poll results, and check pricing across 3 model variants from Claude Code, Codex, Cursor, and VS Code.

What you get

Flux API access for AI agents: run image generation operations, poll asynchronous results, and check pricing through one focused MCP server.

What the assistant can call

Once Flux is connected, these are the calls the assistant has available:

  • remix_image — Yes
  • text_to_image — Yes
  • get_task — Yes
  • check_pricing — No

Configuration and credentials

You will need one environment variable: RUNAPI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at @runapi.ai/flux-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Flux's toolset — remix_image, text_to_image, get_task and 1 more — is a fair guide to whether it matches your workflow. It is maintained by runapi-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the flux mcp server does with a few real requests.

Available tools

ToolWhat it does
remix_imageYes
text_to_imageYes
get_taskYes
check_pricingNo

How to install the Flux MCP server

{
  "mcpServers": {
    "flux-1": {
      "command": "npx",
      "args": ["-y", "@runapi.ai/flux-mcp"],
      "env": {
        "RUNAPI_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
RUNAPI_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Flux to remix image.
  • Use Flux to text to image.
  • Use Flux to get task.

Frequently asked questions

It connects Flux to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (remix_image, text_to_image, get_task, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Flux directly.