4K video generation via Google VEO 3.1: text-to-video, image-to-video, video extension
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
uvx veo-mcp-serverAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-u2n4-veo-mcp-server": {
"command": "uvx",
"args": [
"veo-mcp-server"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
VEO 3.1 is an MCP server for 4K video generation via Google VEO 3.1: text-to-video, image-to-video, video extension. It supports STDIO transport.
Use the generated config in Install. This server runs with uvx veo-mcp-server; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for uvx veo-mcp-server. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for uvx veo-mcp-server. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for uvx veo-mcp-server. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for uvx veo-mcp-server. Add required environment variables before starting Cursor or VS Code.
VEO 3.1 uses STDIO transport. Use the package or command config in Install.
VEO 3.1 inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
VEO 3.1 does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
veo-mcp-serverstdio | pypi | 1.1.2 | None advertised |