maginary-mcp
OfficialRelated Servers
Alternatives to maginary-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to generate and upscale AI images, videos, music, and sound effects, manage generation jobs, access model catalogs, and track credits.3MIT

@retomagic/mcpofficial
AlicenseAqualityCmaintenanceEnables image and video generation through the Magicly API using any MCP client. Supports listing models, generating media, and polling predictions.314 npmMIT- AlicenseAqualityCmaintenanceEnables image and video generation through the SimpleNGAT API, including text/image-to-video, voice-driven video, image upscaling, and health checks, from MCP-compatible clients.8MIT

@callirra/mcpofficial
AlicenseBqualityBmaintenanceEnables MCP-compatible agents to discover models, generate images and videos, use Prompt Studio, upload references, poll tasks, and check balances via the Callirra API.13390 npm1MIT- FlicenseAqualityCmaintenanceEnables browsing Hedra's model catalog and managing AI generation jobs, including submitting, polling, and uploading files, through MCP clients.14-
- AlicenseNot gradedqualityDmaintenanceWraps Flow2API / OpenAI-compatible image generation upstream into an MCP service, providing image generation, history, and caching tools.12MIT
TDQS
Scored across 13 tools
Tools are mostly distinct: parameter discovery, generation lifecycle, account management, and billing each form clear clusters. Minor overlap exists between check_account_status and get_balance, which both report credits_remaining and uploads_remaining, and generate/get_generation/wait_for_generation require careful reading but are sufficiently differentiated.
Most tools follow a clear verb_noun snake_case pattern: list_parameters, get_parameter, create_account, manage_api_key, get_products. The exceptions are the bare verbs generate and checkout, which are still readable but deviate slightly from the otherwise consistent convention.
13 tools is well-scoped for a service that covers prompt-DSL parameter discovery, generation submission and polling, account onboarding, API key management, and purchasing. Each tool serves a distinct functional area without excessive fragmentation or redundancy.
The core workflow is covered end-to-end: discover parameters, generate, poll for completion, fetch results, create an account, obtain an API key, check balance, and purchase credits. Minor gaps include no way to list past generations or cancel an in-progress generation, but these are not fatal to the primary use case.