Schema | Flux MCP Server

Flux MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`RUNAPI_API_KEY`	No	Useful for headless and CI hosts. The server resolves auth in this order: 1. RUNAPI_API_KEY environment variable; 2. ~/.config/runapi/config.json, created by the MCP login tool or runapi login; 3. No key, which still allows check_pricing. A pre-provisioned headless config can use {"apiKey": "your_runapi_key"}.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }
`logging`	{}

Functions exposed to the LLM to take actions

Name	Description
loginA	Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.
remix_imageC	Create a Flux task on RunAPI (remix image). Returns a task id, status, and output URLs.
text_to_imageB	Create a Flux task on RunAPI (text to image). Returns a task id, status, and output URLs.
get_taskA	Fetch the current status and latest result payload for a flux task.
check_pricingA	Look up RunAPI pricing for the flux model line.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runapi-ai/flux-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server