Mcp Veo
Generate short AI videos from prompts inside Claude Code or Cursor when you need launch clips, demos, or social content without leaving the agent.
Overview
mcp-veo is an MCP server for the Grow phase that lets coding agents call Google Veo AI video generation through Ace Data Cloud.
What is this MCP server?
- Bridges Google Veo video generation into MCP tools your coding agent can invoke
- Hosted streamable-http remote at veo.mcp.acedata.cloud plus local stdio via uvx (mcp-veo on PyPI)
- Requires ACEDATACLOUD_API_TOKEN from Ace Data Cloud platform
- Versioned server schema (2026.6.9.4) with GitHub source VeoMCP
- MCP integration for agents—not a standalone video editor UI
- Server version 2026.6.9.4
- Two transports: streamable-http remote and stdio PyPI package mcp-veo
- One required secret env var: ACEDATACLOUD_API_TOKEN
What problem does it solve?
You want agent-generated marketing or demo video without manually copying prompts into Google’s Veo UI and re-uploading assets.
Who is it for?
Indie builders automating short-form video drafts for launches and content calendars who already use MCP in Claude Code or Cursor.
Skip if: Teams needing frame-accurate editorial, licensed stock compliance, or fully offline video pipelines without a cloud API token.
What do I get? / Deliverables
Your agent can request Veo renders from MCP so video drafts sit alongside code and copy in one workspace.
- Agent-invoked Veo video generation jobs via MCP tools
- Repeatable remote or stdio MCP registration for video workflows
Recommended MCP Servers
Journey fit
Grow is where solo builders turn product narrative into repeatable media; Veo fits the content subphase as a generation backend agents can call on demand. Content is the canonical shelf for text-to-video workflows that feed newsletters, landing updates, and distribution—not core app runtime code.
How it compares
MCP bridge to Veo via Ace Data Cloud—not a CapCut-style NLE or a general-purpose agent skill.
Common Questions / FAQ
Who is mcp-veo for?
Solo and small-team builders who use MCP-enabled agents and want Google Veo video generation callable from the same session as code and docs.
When should I use mcp-veo?
Use it during grow and launch content work when you need quick AI video iterations from text prompts tied to a product narrative.
How do I add mcp-veo to my agent?
Register the remote URL https://veo.mcp.acedata.cloud/mcp or add the PyPI package mcp-veo with uvx stdio transport and set ACEDATACLOUD_API_TOKEN in your MCP client config.