Skip to main content
Glama

An MCP server that gives Claude Code, Claude Desktop or any other MCP client video generation with Google Veo. It talks to the Gemini API directly: text-to-video, image-to-video and a transition between a first and a last frame. The MP4 is saved on the machine that runs the server.

Tools

  • generate_video starts a render, waits for it and saves the MP4. Takes a prompt and, optionally:

    • image, the first frame (png, jpg, webp), and lastFrame, which needs image;

    • negativePrompt, seed;

    • aspectRatio: 16:9 (default) or 9:16;

    • durationSeconds: 4, 6 or 8 (default); 1080p and 4k need 8;

    • resolution: 720p (default), 1080p or 4k;

    • model (veo-3.1-generate-preview by default), filename, outputDir.

    Returns the file path. While it waits, it sends MCP progress notifications, so the client doesn't time the call out.

  • fetch_video waits for a render that is already running and saves it by its operation name. When generate_video fails after the render started, its error names the operation: fetch_video picks it up without paying twice.

  • list_models lists the Veo models your key can use.

Veo is billed per second of video and a render takes one to five minutes, so the tool asks the model to check before generating several variants. Network errors, 429 and 5xx are retried with backoff. When the safety filter drops a video, the error says why.

Related MCP server: Vidu MCP

Setup

Node 26 or newer. Add the server to your MCP config, see .mcp.json.example:

{
	"mcpServers": {
		"veo": {
			"command": "npx",
			"args": ["-y", "@aimuzov/veo-mcp"],
			"env": { "GEMINI_API_KEY": "your-api-key", "VEO_OUTPUT_DIR": "./veo" }
		}
	}
}

Get a key at AI Studio, Veo needs a project with billing enabled. Without a key the server still starts, and every tool answers with that hint.

The server runs only over stdio: a video is a file on the disk of the machine that made it, a hosted connector would leave it on someone else's server.

Variable

Default

What it does

GEMINI_API_KEY

Gemini API key, required

VEO_OUTPUT_DIR

./veo

Where videos are saved

VEO_POLL_INTERVAL_MS

10000

How often to poll the render

VEO_TIMEOUT_MS

900000

When to give up on a render

LOG_LEVEL

info

error, warn, info or debug

Development

npm install
npm start          # the TypeScript sources over stdio, no build
npm test
npm run lint
npm run typecheck
npm run build      # build/ for the npm package

Shared helpers and the CI steps come from infra-mcp-kit, formatting and lint rules from infra-site-kit.

License

MIT

Available Tools

3 tools
fetch_videoFetch a Veo video by operationA

Wait for an already started Veo operation and save its video. Use it when generate_video failed after the render had started: its error names the operation. Costs nothing extra.

Inputs: operation (required), filename, outputDir.

generate_videoGenerate a video with VeoA

Generate a video from a text prompt with Google Veo, optionally starting from an image (image-to-video) and ending on another one. Paid per second of video and takes 1-5 minutes, so ask before generating several variants. Saves an MP4 to disk and returns its path.

Inputs: prompt (required), seed, image, model, +7 more.

list_modelsList Veo modelsA

List Veo model ids available to this API key.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: list_models discovers model ids, generate_video starts a paid render, and fetch_video recovers an already-started operation. The descriptions explicitly distinguish starting a new render from fetching an existing one.

    Naming Consistency5/5

    All three tools follow a consistent snake_case verb_noun pattern: list_models, generate_video, fetch_video. There is no mixing of conventions or vague standalone verbs.

    Tool Count5/5

    Three tools is a tight, well-scoped surface for a video-generation server: discovery, generation, and recovery are each covered without redundancy. No tool feels extraneous.

    Completeness4/5

    The core workflow is covered: list available models, generate text/image-to-video, and fetch a video from a started operation. Minor gaps exist around operation management, such as checking status without fetching or cancelling a render, but these are not critical for the stated use case.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers