mcp-veo
io.github.AceDataCloud/mcp-veoVersion 2026.11.1.0MCP server for Google Veo AI video generation
Status
Sign-in required1366 msReachable. It asks for authorization, so we did not look inside.- Last checked
- Nov 14, 2026, 14:35 UTC
- Latency
- 1366 ms
- Remotes responding
- 1 of 1
- Sign-in
- OAuth sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://veo.mcp.acedata.cloud/mcpSign-in required1366 msOAuth sign-in
Claude Code
This server asks for sign-in. Your client opens the sign-in when it connects.
claude mcp add --transport http mcp-veo https://veo.mcp.acedata.cloud/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: mcp-veo
Remote MCP server URL: https://veo.mcp.acedata.cloud/mcpCursor
{
"mcpServers": {
"mcp-veo": {
"url": "https://veo.mcp.acedata.cloud/mcp"
}
}
}VS Code
code --add-mcp '{"name":"mcp-veo","type":"http","url":"https://veo.mcp.acedata.cloud/mcp"}'Streamable HTTP
pypi: mcp-veo 2026.11.1.0Package only
PyPI (uvx)
claude mcp add mcp-veo -e 'ACEDATACLOUD_API_TOKEN=<YOUR_ACEDATACLOUD_API_TOKEN>' -- uvx mcp-veo==2026.11.1.0Replace <YOUR_ACEDATACLOUD_API_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
Tools are visible after sign-in; we do not look inside protected servers.
Details
- Registry status
- Active
- Published
- Nov 1, 2026
- Updated
- Nov 1, 2026
- Categories (suggested)
- Design and mediaSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared