Medhā MCP
Related Servers
Alternatives to Medhā MCP
No user-submitted related servers found.
Related Servers
AlicenseBqualityCmaintenanceProvides 31 tools and 3 resources to access Venice's uncensored AI models for chat, image, video, audio, music, and more, enabling any MCP host to interact with the Venice API.3180 npm68MIT- AlicenseAqualityDmaintenanceMCP server for Krea.ai enabling AI image and video generation using models like Flux, Hailuo, Runway, Kling, and others via natural language prompts.915 npm10Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to generate images and videos through Google Flow using models like Veo and Nano Banana, with tools for image generation, upscaling, video creation, character management, and music generation.7-
- AlicenseAqualityDmaintenanceMCP server for AI-powered media generation: images, videos, audio, and upscaling using 99 AI models.6MIT
- AlicenseAqualityBmaintenanceMCP server for AI-powered image, audio, and video generation, enabling media creation directly from Claude, Cursor, and other MCP clients.1155 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI assistants to generate images and videos on demand using free-tier providers like Agnes AI, Cloudflare Workers AI, Hugging Face, and Google Gemini, with tools for creating media, polling async jobs, and listing providers.-
TDQS
Scored across 31 tools
Most tools are clearly distinct by domain (chat, image, video, music, web, voice, crypto, x402). However, venice_chat and venice_responses overlap significantly — both are chat completions with nearly identical operator preferences and uncensored behavior. Similarly, venice_video_status/venice_music_status and venice_video_complete/venice_music_complete follow parallel but separate verbs that are easy to confuse across media types. The image_edit vs image_multi_edit distinction is reasonably clear, but chat vs responses and the parallel status/complete pairs introduce ambiguity.
The naming follows a strong venice_<domain>_<action> pattern consistently (venice_image_generate, venice_video_status, venice_music_complete, venice_web_search). The domain prefix is uniformly applied to all 31 tools. Minor inconsistency: some tools use generic verbs (chat, asr, tts) while others use domain+verb, and venice_voice_clone uses 'manage' semantics differently from venice_image_styles. Overall highly predictable but with minor phrasing variations.
31 tools is quite heavy for a single server surface. While the underlying Venice API is genuinely broad (chat, images, video, music, voice, web, crypto, x402 billing), the server bundles what could be several focused MCP servers into one, exceeding the comfortable range. The count feels bloated, especially with 5 different x402/crypto tools and 4 video tools plus 4 music tools that duplicate the lifecycle pattern.
The surface is remarkably comprehensive, covering chat, images (generate/edit/multi-edit/upscale/remove-bg/styles), video (generate/status/complete/quote), music (generate/status/complete/quote), voice (TTS/asr/clone), text parsing, web search/scrape, embeddings, and x402 billing. Minor gaps: text parsing accepts URLs but there's no direct file-upload handler for documents, and there's no image generation status polling since it's synchronous, which is fine. The x402 billing flow stops at step-1 direction without steps 2-3, which is acknowledged as external.