MCP for Video- or Image-Generation with Google VEO2
MCP for Video- or Image-Generation with Google VEO2. That is what the mcp video generation with veo2 mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This project implements a Model Context Protocol (MCP) server that exposes Google's Veo2 video generation capabilities. It allows clients to generate videos from text prompts or images, and access the generated videos through MCP resources.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 4 tools. What each one is for:
generateVideoFromText — Parameters: - prompt (string): The text prompt for video generation - config (object, optional): Configuration options - aspectRatio (stringgenerateVideoFromImage — Parameters: - image (string): Base64-encoded image data - prompt (string, optional): Text prompt to guide the video generation - config (objectlistGeneratedVideos — The listGeneratedVideos tool exposed by this serverBuilding — The Building tool exposed by this serverConfiguration is passed through the environment: GOOGLE_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Video Generation With Veo2's toolset — generateVideoFromText, generateVideoFromImage, listGeneratedVideos and 1 more — is a fair guide to whether it matches your workflow. It is maintained by mario-andreschak; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| generateVideoFromText | Parameters: - prompt (string): The text prompt for video generation - config (object, optional): Configuration options - aspectRatio (string, optional): "16:9" or "9:16" - personGeneration (string, optional): "dont_allow |
| generateVideoFromImage | Parameters: - image (string): Base64-encoded image data - prompt (string, optional): Text prompt to guide the video generation - config (object, optional): Configuration options (same as above, but personGeneration only |
| listGeneratedVideos | The listGeneratedVideos tool exposed by this server. |
| Building | The Building tool exposed by this server. |
{
"mcpServers": {
"veo2": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"GOOGLE_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.