A
licenseB
qualityA
maintenanceProvides AI agents with Midjourney API access for image and video generation, task polling, and pricing checks through a focused MCP server.
10
55 npm
1
Apache 2.0
RunAPI Qwen Image MCP Server
Officialby runapi-ai
Related Servers
Alternatives to RunAPI Qwen Image MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for GPT-4o Image model line, enabling text-to-image task creation, status polling, and pricing checks via RunAPI.4110 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to run Flux image generation tasks, poll results, and check pricing through a single MCP server.551 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server for generating images via Zhipu CogView, supporting synchronous and asynchronous generation with progress notifications, plus health check endpoints.-
- AlicenseAqualityAmaintenanceEnables image editing, remixing, and text-to-image generation using Qwen 2 models via RunAPI. Supports task polling and pricing checks.572 npmApache 2.0
- AlicenseAqualityAmaintenanceRunAPI MCP server for the Imagen 4 model line. Create tasks, poll their status, and check pricing through a single RunAPI API key.565 npmApache 2.0
TDQS
A3.6/5.0
Scored across 6 tools
Disambiguation4/5
The three image generation tools (text_to_image, edit_image, remix_image) could be confused since they all create Qwen Image tasks returning similar payloads, but their action-prefix names do clearly distinguish the three modes. login, get_task, and check_pricing are distinct concerns. Only the generation trio has mild boundary ambiguity.
Naming Consistency5/5
All tools consistently follow a clear snake_case verb-first convention: login, edit_image, remix_image, text_to_image (verb or noun phrase prefix), get_task, check_pricing. There is a uniform action-oriented pattern with no mixed casing or style deviations.
Tool Count5/5
Six tools is a well-scoped surface for an image-generation API wrapper: auth, three generation modes, task status polling, and pricing lookup. Each tool earns its place and none feel redundant or unnecessary.
Completeness4/5
The surface covers the core lifecycle: authentication, generation in three modes, task polling, and pricing. Minor gaps exist—no explicit cancel/delete task or batch operations—but the primary workflows are fully supported and there are no dead ends.
Maintenance
ActivitySlowing
ResponsivenessNo issues