claude-media-mcp
Related Servers
Alternatives to claude-media-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables video and image generation from any MCP client, with support for models like Veo 3.1, Grok Imagine, and Nano Banana, including text-to-video, image-to-video, image generation and editing.4MIT
- AlicenseAqualityCmaintenanceMulti-provider media generation MCP server that generates images, videos, audio, and transcriptions from text prompts using OpenAI, xAI, Gemini, ElevenLabs, and BFL through a single unified interface.658 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables any MCP-capable agent to generate images in the cloud without a GPU, local models, or downloads, using the user's own API key for providers such as DashScope's Wan/Qwen image models and Volcano Ark's Seedream. It can list which channels are configured and return generated image links or save the files to a local directory, all locally over stdio.MIT
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client to search and submit tasks across 350+ multimodal image, video, audio, and 3D models, run ComfyUI workflows and AI apps, upload/download files, and chat with LLMs. It supports stdio MCP integration and optional scope trimming for image, video, or audio only.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to generate images and videos, synthesize speech, clone and design voices, and dynamically configure API interactions.280 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients like Claude and ChatGPT to generate images and videos, animate images, create lip-synced videos, list TTS voices, and manage media via remote MCP tools.-
TDQS
Scored across 4 tools
Each tool targets a distinct modality and action: generate_image (images), generate_audio (audio), and the start_video/check_video pair form a clearly documented async lifecycle. The start/check pairing is explicitly cross-referenced in both descriptions, so there is no risk of misselection.
All four names follow a strict verb_noun snake_case pattern (generate_image, generate_audio, start_video, check_video). The verbs accurately reflect each tool's role, and the async pair uses a clean start/check convention rather than an inconsistent verb.
Four tools is well-scoped for a media generation server covering image, audio, and video. Each tool earns its place: one per modality plus the necessary polling companion for the async video job.
The core generation lifecycle for images (including edits via input_images), audio (including prompt-based fal models), and video is fully covered. Minor gaps remain, such as no job cancellation, job listing, or file cleanup, but agents can work around these.