pmind-veo-mcp
Related Servers
Alternatives to pmind-veo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables video generation from text prompts or images using Google's Veo 3 API. Supports multiple models, audio generation, and various aspect ratios for creating high-quality videos.3MIT
- FlicenseAqualityDmaintenanceEnables high-quality AI video generation using Google's Veo 3.1 model for text-to-video, style-guided, and frame-interpolation tasks. It features token-efficient reference image handling, batch processing, and video extension capabilities with built-in cost estimation.62-
- AlicenseNot gradedqualityDmaintenanceGenerates videos using Google Gemini Veo from text prompts with optional aspect ratio settings.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI image and video generation using Google Vertex AI's Imagen and Veo models, with support for configurable parameters and local storage.1MIT
- AlicenseAqualityBmaintenanceEnables video generation using Google AI tools (Veo, Nano Banana) via the Model Context Protocol, with browser automation powered by Playwright.24MIT
- AlicenseAqualityCmaintenanceEnables AI image generation and editing using Google's Gemini Multimodal Image APIs.61MIT
TDQS
Scored across 6 tools
The tools are mostly distinct, but veo_list_generations and veo_list_sessions have identical descriptions, making them impossible to differentiate. This redundancy creates clear ambiguity for an agent selecting which to use.
All six tools follow the veo_verb_noun pattern consistently, with clear verbs like generate, check, list, cleanup, and download. There is no mixing of styles or vague naming.
With six tools, the server is well-scoped for video generation workflows. The count covers generation, status checking, listing, downloading, and cleanup without being excessive or thin.
The core lifecycle (generate, check, list, download, cleanup) is covered, but there is no cancel/delete operation, and the description mentions veo_check_operation which is not actually exposed. These gaps could frustrate agents needing abort or granular API status.