Loomal

4K video generation via Google VEO 3.1: text-to-video, image-to-video, video extension

1 starspypi: veo-mcp-server

About VEO 3.1

VEO 3.1 is an MCP (Model Context Protocol) server published by u2n4 in the official MCP registry. 4K video generation via Google VEO 3.1: text-to-video, image-to-video, video extension

It ships as a Python package on PyPI (veo-mcp-server), so any MCP client that can launch a local process can run it.

Development happens in the open at github.com/u2n4/gemini-media-mcp, where the project has earned 1 GitHub stars.

Use VEO 3.1 with your agent

Claude Code · one command
claude mcp add veo-3-1 -- uvx veo-mcp-server
Claude Desktop, Cursor & other MCP clients · config
{
  "mcpServers": {
    "veo-3-1": {
      "command": "uvx",
      "args": [
        "veo-mcp-server"
      ]
    }
  }
}
pypiveo-mcp-server

Frequently asked questions

What is VEO 3.1?
VEO 3.1 is an MCP (Model Context Protocol) server by u2n4. 4K video generation via Google VEO 3.1: text-to-video, image-to-video, video extension
How do I connect VEO 3.1 to Claude, Cursor, or another MCP client?
Install VEO 3.1 from its pypi package (veo-mcp-server) and register it under "mcpServers" in your client's MCP configuration — for example claude_desktop_config.json or Cursor's mcp.json — then restart the client.
Is VEO 3.1 open source?
Yes — the source code is public at github.com/u2n4/gemini-media-mcp, with 1 GitHub stars.
Can AI agents pay to use VEO 3.1?
Not yet through Loomal — VEO 3.1 is listed as a free directory entry. If its maintainer verifies ownership, they can set per-call USDC pricing that agents pay over x402, with settlement on Base.

Listing data from the official MCP registry and GitHub, refreshed periodically. Not affiliated with the maintainer unless claimed. Maintain VEO 3.1? Claim this listing free by verifying GitHub ownership, or contact us.