Venice MCP Server
OfficialRelated Servers
Alternatives to Venice MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceOperator-tuned MCP server for Venice AI, providing 31 tools for chat, image, video, audio, and music generation with curated presets and workflow prompts.31MIT

aicut MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables generating AI videos, images, audio, and staged story episodes directly from Claude, ChatGPT, Cursor, Grok, or any MCP client, with 61 tools covering model catalogs, generation jobs, and media transforms such as upscaling, lipsync, motion control, and video editing. Hosted over Streamable HTTP with OAuth sign-in, so no API key or local installation is required.MIT- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to generate images and videos, synthesize speech, clone and design voices, and dynamically configure API interactions.635 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.478 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides 20 essential tools including HTTP requests, web search, file I/O, shell commands, and persistent memory for any MCP client, with zero configuration required.MIT
TDQS
Scored across 45 tools
Most tools target a clearly distinct resource+operation (image_generate vs image_edit vs image_upscale, video_status vs video_complete), so an agent can usually pick correctly. The main soft spots are the three chat entry points (venice_chat, venice_responses, venice_chat_with_character) and the near-overlapping venice_api_key_rate_limits vs venice_get_api_key, which also reports rate limits, plus four model-metadata tools whose boundaries require careful reading.
Casing and the `venice_` prefix are perfectly consistent snake_case, which helps a lot. However word order is mixed: noun-first compounds (venice_image_generate, venice_billing_balance, venice_model_details) coexist with verb-first (venice_list_models, venice_get_character, venice_list_api_keys) and bare acronym names (venice_tts, venice_asr, venice_chat), so the pattern is readable but not predictable.
45 tools is heavy, but the server fronts a genuinely broad platform (text, image, video, music, audio, search, crypto RPC, TEE, characters, billing, x402), so most tools map to a real endpoint. There is still consolidation slack: four model-metadata tools, three API-key tools, four billing tools, and paired quote/status/complete triples could be collapsed.
Coverage is unusually thorough: generation, polling, and cleanup exist for both video and music, plus image transforms, TTS/ASR/voice cloning, search/scrape, model discovery, billing, and x402 auth paths. Minor gaps remain, notably no API-key creation/rotation or revocation, and no character creation, but agents can work around these via other channels.