AceDataCloud/MCPFlux

A Model Context Protocol (MCP) server for AI image generation and editing using Flux through the AceDataCloud platform.
Generate and edit stunning AI images with Flux models (flux-dev, flux-pro, flux-kontext) directly from Claude, Cursor, or any MCP-compatible client.
Features
- **Image Generation** - Generate images from text prompts with 6 Flux models
- **Image Editing** - Edit existing images with context-aware Flux Kontext models
- **Task Management** - Track async generation tasks and batch status queries
- **Model Guide** - Built-in model selection and prompt writing guidance
- **Dual Transport** - stdio (local) and HTTP (remote/cloud) modes
- **Docker Ready** - Containerized with K8s deployment manifests
- **Secure** - Bearer token auth with per-request isolation in HTTP mode
Tool Reference
| Tool | Description |
|------|-------------|
| flux_generate_image | Generate AI images from a text prompt using Flux. |
| flux_edit_image | Edit an existing image using Flux with a text prompt. |
| flux_list_models | List all available Flux models and their capabilities. |
| flux_list_actions | List all available Flux tools and their use cases. |
| flux_get_task | Query the status and result of a Flux image generation task. |
| flux_get_tasks_batch | Query multiple Flux image generation tasks at once. |
Connect: hosted OAuth, API token, or local stdio
The hosted endpoint is https://flux.mcp.acedata.cloud/mcp. Choose one route for the MCP client:
| Route | When to use it | Credential setup |
|---|---|---|
| Hosted OAuth | The client supports remote MCP OAuth | Add only the URL, then sign in to AceDataCloud and approve access. No token needs to be pasted into client configuration. |
| Hosted API token | The client cannot finish OAuth, or you need an explicit integration credential | Send an AceDataCloud API token in the Authorization: Bearer … header. Keep it in a local secret store or environment variable. |
| Local stdio | The client runs a local MCP process | Install mcp-flux-pro and pass ACEDATACLOUD_API_TOKEN to that process. It still calls the AceDataCloud API. |
The hosted service advertises OAuth metadata and Dynamic Client Registration (DCR). **DCR registers the client application; it is not an API key.** OAuth signs you in and the client sends the resulting Bearer token; it may reuse or create an API credential for the account. Browser sign-in still requires an AceDataCloud account. The hosted service can be metered: review current service documentation and displayed pricing before a real operation. Do not configure both an OAuth login and a fixed Authorization header for the same server.
Hosted OAuth examples
- **Claude and Claude Desktop chat:** Add a remote custom connector in Customize → Connectors → Add custom connector, enter https://flux.mcp.acedata.cloud/mcp, select sign-in, and choose **Register automatically** if Claude asks how to register its OAuth client. Complete consent. Claude Desktop's local claude_desktop_config.json is a separate setup. Claude connector guide.
- **Claude Code:** claude mcp add --transport http --scope user flux https://flux.mcp.acedata.cloud/mcp, then claude mcp login flux. Check /mcp. Claude Code MCP guide.
- **Cursor:** Add a remote server with only https://flux.mcp.acedata.cloud/mcp. For a project, merge the entry below into /.cursor/mcp.json; for personal use, use ~/.cursor/mcp.json. Cursor MCP guide.
- **VS Code / Copilot:** Run **MCP: Add Server**, select HTTP, enter https://flux.mcp.acedata.cloud/mcp, then finish the browser sign-in. New portable workspace configs use /.mcp.json; the VS Code-specific format below uses /.vscode/mcp.json or the user profile. Check **MCP: List Servers**. VS Code MCP setup.
- **Codex:** codex mcp add flux --url https://flux.mcp.acedata.cloud/mcp, then codex mcp login flux. Its user settings are in ~/.codex/config.toml. Official Codex MCP guide.