@runapi.ai/flux-kontext-mcp
Related Servers
Alternatives to @runapi.ai/flux-kontext-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceRunAPI MCP server for the Flux 2 model line. Create tasks, poll their status, and check pricing through a single RunAPI API key.532 npmApache 2.0- AlicenseNot gradedqualityDmaintenanceImplements a Model Context Protocol (MCP) server powered by Flux API from Cephalon Cloud, enabling users to utilize advanced AI capabilities through standardized communication.31MIT
- AlicenseNot gradedqualityDmaintenanceA server that enables generating images through the Replicate API by calling the Flux Schnell model via the Model Context Protocol (MCP).3MIT
- FlicenseBqualityDmaintenanceAn MCP image generation server based on the Flux Schnell model that provides API access for generating images from text prompts with customizable dimensions and seeds.11-
- AlicenseAqualityBmaintenanceEnables AI agents to run Flux image generation tasks, poll results, and check pricing through a single MCP server.526 npmApache 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables high-quality image generation using the Flux.1 Schnell model via Together AI with customizable parameters.138 npm10MIT
TDQS
Scored across 4 tools
Each tool has a clear, unique purpose: login handles authentication, text_to_image creates tasks, get_task retrieves task status, and check_pricing provides pricing info. There is no overlap or ambiguity between them.
All tool names use consistent snake_case and follow clear verb-based patterns (e.g., text_to_image, get_task, check_pricing). The naming is predictable and easy to understand.
With 4 tools, the server is well-scoped for its purpose: authentication, image generation, task polling, and pricing lookup. This is a focused and efficient set without unnecessary extras.
The tools cover the essential lifecycle: authenticate, create a task, check status, and get pricing. A minor gap is the lack of a list all tasks tool, which may require users to remember task IDs, but core workflows are supported.