
Research
/Security News
Popular npm Packages in the keyv and Cacheable Namespaces Compromised in Active Supply Chain Attack
Popular npm packages keyv and cacheable compromised.
mcp-veo
Advanced tools
A Model Context Protocol (MCP) server for AI video generation using Veo through the AceDataCloud API.
Generate AI videos from text prompts or images directly from Claude, VS Code, or any MCP-compatible client.
| Tool | Description |
|---|---|
veo_text_to_video | Generate AI video from a text prompt using Veo. |
veo_image_to_video | Generate AI video from one or more reference images using Veo. |
veo_get_1080p | Get the 1080p high-resolution version of a generated video. |
veo_get_task | Query the status and result of a video generation task. |
veo_get_tasks_batch | Query multiple video generation tasks at once. |
veo_list_models | List all available Veo models and their capabilities. |
veo_list_actions | List all available Veo API actions and corresponding tools. |
veo_get_prompt_guide | Get guidance on writing effective prompts for Veo video generation. |
AceDataCloud hosts a managed MCP server — no local installation required.
Endpoint: https://veo.mcp.acedata.cloud/mcp
All requests require a Bearer token. Use the API token from Step 1.
Connect directly on Claude.ai with OAuth — no API token needed:
https://veo.mcp.acedata.cloud/mcpAdd to your config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"veo": {
"type": "streamable-http",
"url": "https://veo.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Add to your MCP config (.cursor/mcp.json or .windsurf/mcp.json):
{
"mcpServers": {
"veo": {
"type": "streamable-http",
"url": "https://veo.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Add to your VS Code MCP config (.vscode/mcp.json):
{
"servers": {
"veo": {
"type": "streamable-http",
"url": "https://veo.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Or install the Ace Data Cloud MCP extension for VS Code, which registers the hosted MCP servers with one-click setup.
{
"mcpServers": {
"veo": {
"url": "https://veo.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Claude Code supports MCP servers natively:
claude mcp add veo --transport http https://veo.mcp.acedata.cloud/mcp \
-h "Authorization: Bearer YOUR_API_TOKEN"
Or add to your project's .mcp.json:
{
"mcpServers": {
"veo": {
"type": "streamable-http",
"url": "https://veo.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Add to Cline's MCP settings (.cline/mcp_settings.json):
{
"mcpServers": {
"veo": {
"type": "streamable-http",
"url": "https://veo.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Add to your MCP configuration:
{
"mcpServers": {
"veo": {
"type": "streamable-http",
"url": "https://veo.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Add to Roo Code MCP settings:
{
"mcpServers": {
"veo": {
"type": "streamable-http",
"url": "https://veo.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
Add to .continue/config.yaml:
mcpServers:
- name: veo
type: streamable-http
url: https://veo.mcp.acedata.cloud/mcp
headers:
Authorization: "Bearer YOUR_API_TOKEN"
Add to Zed's settings (~/.config/zed/settings.json):
{
"language_models": {
"mcp_servers": {
"veo": {
"url": "https://veo.mcp.acedata.cloud/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_TOKEN"
}
}
}
}
}
# Health check (no auth required)
curl https://veo.mcp.acedata.cloud/health
# MCP initialize
curl -X POST https://veo.mcp.acedata.cloud/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'
If you prefer to run the server on your own machine:
# Install from PyPI
pip install mcp-veo
# or
uvx mcp-veo
# Set your API token
export ACEDATACLOUD_API_TOKEN="your_token_here"
# Run (stdio mode for Claude Desktop / local clients)
mcp-veo
# Run (HTTP mode for remote access)
mcp-veo --transport http --port 8000
{
"mcpServers": {
"veo": {
"command": "uvx",
"args": ["mcp-veo"],
"env": {
"ACEDATACLOUD_API_TOKEN": "your_token_here"
}
}
}
}
docker pull ghcr.io/acedatacloud/mcp-veo:latest
docker run -p 8000:8000 ghcr.io/acedatacloud/mcp-veo:latest
Clients connect with their own Bearer token — the server extracts the token from each request's Authorization header.
| Tool | Description |
|---|---|
veo_text_to_video | Generate video from a text prompt |
veo_image_to_video | Generate video from reference image(s) |
veo_get_1080p | Get high-resolution 1080p version |
| Tool | Description |
|---|---|
veo_get_task | Query a single task status |
veo_get_tasks_batch | Query multiple tasks at once |
| Tool | Description |
|---|---|
veo_list_models | List available Veo models |
veo_list_actions | List available API actions |
veo_get_prompt_guide | Get video prompt writing guide |
User: Create a video of a sunset over the ocean
Claude: I'll generate a sunset video for you.
[Calls veo_text_to_video with prompt="Cinematic shot of a golden sunset over the ocean, waves gently rolling, warm colors reflecting on the water"]
User: Animate this product image to make it rotate slowly
Claude: I'll create a video from your image.
[Calls veo_image_to_video with image_urls=["product_image.jpg"], prompt="Product slowly rotates 360 degrees, studio lighting"]
User: Create a video that transitions between these two landscape photos
Claude: I'll create a transition video between your images.
[Calls veo_image_to_video with image_urls=["img1.jpg", "img2.jpg"], prompt="Smooth cinematic transition between scenes"]
| Model | Text2Video | Image2Video | Image Input |
|---|---|---|---|
veo3 | ✅ | ✅ | 1-3 images |
veo3-fast | ✅ | ✅ | 1-3 images |
veo31 | ✅ | ✅ | 1-3 images |
veo31-fast | ✅ | ✅ | 1-3 images |
veo31-fast-ingredients | ❌ | ✅ | 1-3 images (fusion) |
Aspect Ratios:
16:9 - Landscape/widescreen (default)9:16 - Portrait/vertical (social media)| Variable | Description | Default |
|---|---|---|
ACEDATACLOUD_API_TOKEN | API token from AceDataCloud | Required |
ACEDATACLOUD_API_BASE_URL | API base URL | https://api.acedata.cloud |
ACEDATACLOUD_OAUTH_CLIENT_ID | OAuth client ID (hosted mode) | — |
ACEDATACLOUD_PLATFORM_BASE_URL | Platform base URL | https://platform.acedata.cloud |
VEO_DEFAULT_MODEL | Default model for generation | veo31-fast |
VEO_REQUEST_TIMEOUT | Request timeout in seconds | 180 |
LOG_LEVEL | Logging level | INFO |
mcp-veo --help
Options:
--version Show version
--transport Transport mode: stdio (default) or http
--port Port for HTTP transport (default: 8000)
# Clone repository
git clone https://github.com/AceDataCloud/VeoMCP.git
cd VeoMCP
# Create virtual environment
python -m venv .venv
source .venv/bin/activate # or `.venv\Scripts\activate` on Windows
# Install with dev dependencies
pip install -e ".[dev,test]"
# Run unit tests
pytest
# Run with coverage
pytest --cov=core --cov=tools
# Run integration tests (requires API token)
pytest tests/test_integration.py -m integration
# Format code
ruff format .
# Lint code
ruff check .
# Type check
mypy core tools
# Install build dependencies
pip install -e ".[release]"
# Build package
python -m build
# Upload to PyPI
twine upload dist/*
VeoMCP/
├── core/ # Core modules
│ ├── __init__.py
│ ├── client.py # HTTP client for Veo API
│ ├── config.py # Configuration management
│ ├── exceptions.py # Custom exceptions
│ ├── server.py # MCP server initialization
│ ├── types.py # Type definitions
│ └── utils.py # Utility functions
├── tools/ # MCP tool definitions
│ ├── __init__.py
│ ├── video_tools.py # Video generation tools
│ ├── info_tools.py # Information tools
│ └── task_tools.py # Task query tools
├── prompts/ # MCP prompts
│ └── __init__.py
├── tests/ # Test suite
│ ├── conftest.py
│ ├── test_client.py
│ ├── test_config.py
│ ├── test_integration.py
│ └── test_utils.py
├── deploy/ # Deployment configs
│ └── production/
│ ├── deployment.yaml
│ ├── ingress.yaml
│ └── service.yaml
├── .env.example # Environment template
├── .gitignore
├── Dockerfile # Docker image for HTTP mode
├── docker-compose.yaml # Docker Compose config
├── LICENSE
├── main.py # Entry point
├── pyproject.toml # Project configuration
└── README.md
This server wraps the AceDataCloud Veo API:
Contributions are welcome! Please:
git checkout -b feature/amazing)git commit -m 'Add amazing feature')git push origin feature/amazing)MIT License - see LICENSE for details.
Made with love by AceDataCloud
FAQs
MCP Server for Veo AI Video Generation via AceDataCloud API
We found that mcp-veo demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
/Security News
Popular npm packages keyv and cacheable compromised.

Security News
A misconfiguration gave three Anthropic models internet access, and one, believing it was in a simulation, shipped a credential-stealing package to PyPI.

Security News
/Company News
Socket has joined the new Composer and Packagist sponsorship program as a launch sponsor, supporting the team that keeps PHP's package ecosystem secure.