What it does
The server exposes Google Veo video generation to MCP-compatible clients such as Claude and VS Code. Its tools cover text-to-video, image-to-video (including animating images, transitions between images and blending several images), and a 1080p version of a generated video. Other tools check the status and result of one or several generation tasks, list the available Veo models and their capabilities, list the API actions behind the tools, and give guidance on writing prompts.
It suits someone who wants to create short AI videos from text descriptions or reference images without leaving an MCP client, or who needs to track generation jobs and choose between Veo models for quality or speed.
The server can be reached in three ways: a hosted endpoint with OAuth sign-in, a hosted endpoint with an AceDataCloud API token sent as a Bearer header, or a local stdio process installed as mcp-veo and given the API token through an environment variable. In every route the server calls the AceDataCloud API. With hosted OAuth, Dynamic Client Registration registers the client application and does not supply an API key.
Limitations and requirements
Browser sign-in requires an AceDataCloud account. The token and local routes need an AceDataCloud API token; a general key can use the services available to the account, while a dedicated application key is limited to its service. The key must allow the generation operations being called, since task lookup does not grant permission to submit a generation, and the account balance must cover requests. The hosted service is metered, so current pricing should be checked before real operations. Do not configure OAuth sign-in and a fixed Authorization header for the same server. Account-management platform tokens cannot replace a generation API key. Keep tokens out of prompts, shared workflows and version control.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 15 Nov 2026 · its page on the source
io.github.AceDataCloud/mcp-veo
MCP server for Google Veo AI video generation
v2026.11.15.0As shown on registry.modelcontextprotocol.io when we last read it