@runapi.ai/flux-2-mcpofficial
A
licenseA
qualityA
maintenanceRunAPI MCP server for the Flux 2 model line. Create tasks, poll their status, and check pricing through a single RunAPI API key.
5
62 npm
Apache 2.0
@runapi.ai/flux-kontext-mcp
by runapi-ai
Related Servers
Alternatives to @runapi.ai/flux-kontext-mcp
No user-submitted related servers found.
Related Servers
- 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.5240 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.152 npm10MIT
TDQS
A3.8/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a distinct purpose: authentication, pricing lookup, task creation, and status retrieval. There is no overlap or ambiguity between the tools, allowing an agent to select the correct one without confusion.
Naming Consistency4/5
Tool names mostly follow a consistent snake_case verb_noun pattern (text_to_image, check_pricing, get_task). The 'login' tool is a single-word exception but is a common and recognizable auth action, so the overall consistency remains strong.
Tool Count5/5
With only 4 tools, the server is well-scoped for a focused flux-kontext image generation client. Each tool serves a necessary role (auth, pricing, creation, status) with no redundancy, making the count appropriate for the domain.
Completeness4/5
The essential workflow of authentication, task creation, and status retrieval is fully covered. Missing operations like cancel or listing past tasks are minor enhancements rather than critical gaps, so the surface is reasonably complete for primary use cases.
Maintenance
ActivityMaintained
ResponsivenessNo issues