A
licenseB
qualityD
maintenanceOperator-tuned MCP server for Venice AI, providing 31 tools for chat, image, video, audio, and music generation with curated presets and workflow prompts.
31
MIT
Venice MCP Server
Officialby veniceai
Related Servers
Alternatives to Venice MCP Server
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to generate images and videos, synthesize speech, clone and design voices, and dynamically configure API interactions.188 npmMIT
- AlicenseAqualityAmaintenanceEnables 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.4479 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
- AlicenseNot gradedqualityBmaintenanceAccess 400+ generative AI models directly from your AI assistant — generate images (FLUX, Midjourney, GPT-4o), create videos (Veo3, Kling), make music (Suno), and enhance photos, all via a single MCP server.12MIT
TDQS
A3.6/5.0
Scored across 45 tools
Disambiguation4/5
Most tools target clearly distinct resources and actions (image_edit vs image_multi_edit, video_status vs music_status, chat vs chat_with_character). A few boundaries are subtle: venice_model_traits vs venice_model_compatibility_mapping seem to return similar trait/name→id mappings, and venice_chat vs venice_responses (alpha) both do text completion, risking misselection.
Naming Consistency5/5
Every tool uses the venice_ prefix with snake_case, and the resource_action pattern (venice_image_generate, venice_video_status, venice_music_generate) is applied predictably across all 45 tools. Deviations like venice_chat, venice_tts, venice_embeddings are accepted module-level names rather than inconsistency.
Tool Count3/5
45 tools is heavy, though justified by a very broad API surface spanning chat, image, video, music, audio, web, models, crypto, TEE, characters, billing, and x402. Grouping is coherent but the set is near the upper bound of what an agent can select from reliably.
Completeness4/5
The surface is extensive: generate/status/complete lifecycles for video and music, full image ops, TTS/ASR/voice cloning, embeddings, model catalog, characters, billing, crypto RPC, and x402 flows. Minor gaps remain (characters are read-only, chat is explicitly non-streaming), but core workflows are covered.
Maintenance
ActivityActive
ResponsivenessUnresponsive