grok-imagine-mcp
Related Servers
Alternatives to grok-imagine-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityFmaintenanceEnables AI video and image generation through the Runway API. Supports video generation from images and text prompts, image creation, video upscaling and editing, and task management.712 npm23MIT- AlicenseAqualityBmaintenanceEnables creating and managing GPT Image tasks (edit and text-to-image) via RunAPI, with options to poll status and check pricing.5293 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables creating and managing Runway video generation tasks (text-to-video, video extension) through a single RunAPI key, including task polling and pricing checks.5228 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables text-to-image generation using Z Image models via RunAPI, with task management and pricing lookup.4206 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables creating and polling Luma video modification tasks, fetching task status, and checking pricing via the RunAPI API.3268 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables image editing, remixing, and text-to-image generation using Qwen 2 models via RunAPI. Supports task polling and pricing checks.5260 npmApache 2.0
TDQS
Scored across 10 tools
The seven task-creation tools share identical boilerplate descriptions ("Create a Grok Imagine task on RunAPI (...)") and identical return shapes, so the agent must rely almost entirely on the tool names to distinguish them. The names themselves are modality-specific (text_to_image vs edit_image vs upscale_image vs image_to_video vs extend_video), which is mostly clear, though 'segment_map' is opaque and edit_image/upscale_image overlap conceptually.
Conventions are mixed: login, get_task, check_pricing, edit_image, extend_video, upscale_image follow a verb_noun style, while text_to_image, image_to_video, text_to_video, and segment_map are noun-phrase/operation names with no verb. It's readable but not a single predictable pattern, and the '_to_' forms sit awkwardly next to the verb-first ones.
Ten tools is well-scoped for an async generation service: one auth tool, one pricing lookup, one status poller, and one tool per generation mode. Each tool earns its place and there is no filler.
Auth, pricing, task polling, and seven generation modes are covered, but the async task lifecycle has notable gaps: there is no list_tasks, cancel_task, or delete, so an agent that loses a task id or needs to cancel a runaway job is stuck. Result retrieval is only via get_task, with no download/save helper.