Google Veo 3.1 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging (default: false) | false |
| OUTPUT_DIR | No | Default output directory (default: ./output) | ./output |
| GOOGLE_API_KEY | Yes | Google API key (required) | |
| VIDEO_POLL_INTERVAL | No | Polling interval in ms (default: 15000) | 15000 |
| VIDEO_MAX_POLL_ATTEMPTS | No | Max polling attempts (default: 120) | 120 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_videoA | Generate a video using Google Veo 3.1 API. Supports:
Models:
Pricing (per second, audio always included):
|
| extend_videoA | Extend an existing video by 7 seconds using Veo 3.1 API. The extension continues from the last second of the input video. Requirements:
Estimated cost: ~$2.80 per extension (7 seconds x $0.40/sec) |
| interpolate_framesA | Generate a video that smoothly transitions between two keyframes using Veo 3.1 API. Creates a video that starts at the first frame and ends at the last frame with AI-generated motion in between. Pricing: Same as generate_video based on duration (audio always included) |
| get_video_statusA | Check the status of a video generation operation. Returns the current status (done/pending) and video URL if completed. Can also download the completed video (use after generate_video with wait: false). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ex-takashima/google-veo3-1-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server