Veo 3 1 Mcp

io.github.runapi-builderPublished by GitHub account runapi-builderv0.2.1Updated Oct 29, 2026

RunAPI MCP server for Veo 3.1: create tasks, poll status, check pricing.

VerifiedSTDIODesktop onlyMedia & DesignAI & ML

Overview

AI-generated overview

RunAPI MCP server scoped to Veo 3.1: lets an assistant create video generation tasks, poll their status, and check pricing.

What you can do
  • Create Veo 3.1 video tasks: text to video, extend an existing video, and upscale video, each optionally waiting for a terminal status
  • Poll tasks: fetch the current status and latest result payload for an existing task by id
  • Check pricing: look up RunAPI pricing for the Veo 3.1 model line and endpoint before submitting
  • Authenticate: run a browser PKCE login that saves the API key to the shared RunAPI config file
When to use it
Use it when an assistant should generate or upscale video through Veo 3.1 on RunAPI and stay scoped to that one model line, rather than loading the full RunAPI catalog. Pricing checks work without signing in, so it is also handy for cost estimates before committing to a task.
Requirements
Runs locally over stdio, typically via npx with the npm package, so Node.js is needed. Task creation and polling need a RunAPI account: either the login tool (browser flow writing to the RunAPI config file) or the RUNAPI_API_KEY environment variable for headless hosts. Network access to RunAPI is required.
Before you install
Task creation spends money on RunAPI, so confirm cost and scope before expensive, long-running, or batch requests. The login tool stores an API key in a config file on disk; keep that file and any RUNAPI_API_KEY value out of version control. Generated media is produced by a third-party service, and the server advises not describing results as if they were inspected.

Installation

In SourceWeft

  1. Open Veo 3 1 Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

RunAPI Veo 3.1 MCP Server

Veo 3.1 API access for AI agents: run video generation operations, poll asynchronous results, and check pricing through one focused MCP server.

Works with Claude Code, Codex, Cursor, Windsurf, VS Code, Roo Code, and any MCP-compatible host.

[npm version] [GitHub repository] [Apache-2.0 license] [MCP Server] [3 models]

Install | Tools | Models | Agent Prompts | Configuration | Links


Why This Package?

@runapi.ai/veo-3-1-mcp is a focused Model Context Protocol server for the Veo 3.1 model line on RunAPI. It gives MCP-compatible assistants direct access to 3 endpoints and 3 model variants without loading the full RunAPI catalog.

Use this per-model server when an agent should stay scoped to Veo 3.1. Use @runapi.ai/mcp when one assistant should discover every RunAPI model line.


Install

Add it to Claude Code:

bash
claude mcp add veo-3-1 -s user -- npx -y @runapi.ai/veo-3-1-mcp

Use project scope when the server should be shared with a repository:

bash
claude mcp add veo-3-1 -s project -- npx -y @runapi.ai/veo-3-1-mcp

Codex, Cursor, Windsurf, VS Code, Roo Code, and other MCP hosts can use the same stdio command:

json
{  "mcpServers": {    "veo-3-1": {      "command": "npx",      "args": ["-y", "@runapi.ai/veo-3-1-mcp"]    }  }}

check_pricing works before sign-in. For task creation and status polling, ask your assistant to call the login tool. It opens a browser login and saves credentials to ~/.config/runapi/config.json, the same file used by runapi login. Headless and CI hosts can still set RUNAPI_API_KEY before starting the MCP host.

Ready-made examples are in examples/ for Claude, Cursor, Windsurf, VS Code, and Roo Code.


Tools

ToolAuthPurpose
extend_videoYesCreate a Veo 3.1 extend video task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
text_to_videoYesCreate a Veo 3.1 text to video task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
upscale_videoYesCreate a Veo 3.1 upscale video task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
get_taskYesFetch the current status and latest payload for an existing task.
check_pricingNoLook up current pricing for a Veo 3.1 model and endpoint.

Models

Veo 3.1 covers 3 model variants across 3 endpoints. Each tool accepts the models listed for it:

ToolModels
extend_videono model parameter
text_to_videoveo-3.1, veo-3.1-fast, veo-3.1-lite
upscale_videono model parameter

Model availability can change between releases. Use check_pricing or the Veo 3.1 model page for the current catalog view.


Agent Prompts

Ask your assistant in natural language; it can inspect pricing, create the task, and return the task id plus output URLs.

Create a task

text
Run a Veo 3.1 extend video task with RunAPI.

The assistant can call check_pricing, then extend_video, and return the task id, status, and output URLs.

Submit without waiting

text
Create the task but don't wait for it to finish.

The assistant calls the create tool with wait: false and returns the task id. Check on it later with get_task.

Check pricing before creating

text
Check current Veo 3.1 pricing, then create the task if it matches my request.

The assistant calls check_pricing and can link to the Veo 3.1 model page for the canonical catalog entry.


Configuration

The server resolves auth in this order:

  1. RUNAPI_API_KEY environment variable, useful for headless and CI hosts
  2. ~/.config/runapi/config.json, created by the MCP login tool or runapi login
  3. No key, which still allows check_pricing

The config file is normally managed by login. A pre-provisioned headless config can use:

json
{  "apiKey": "your_runapi_key"}

Do not commit real API keys.


Links

ResourceURL
Veo 3.1 model pagehttps://runapi.ai/models/veo-3.1
npm package@runapi.ai/veo-3-1-mcp
GitHub repositoryrunapi-ai/veo-3-1-mcp
RunAPI MCP overviewrunapi.ai/mcp
RunAPI docsrunapi.ai/docs

License

Licensed under the Apache License, Version 2.0.

Source: README.md at commit fdaf0a4

Tools

6

login

Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.

Parametersforce

extend_video

Create a Veo 3.1 task on RunAPI (extend video). Returns a task id, status, and output URLs.

Parameterswaitseedspromptwatermarktimeout_mscallback_urlsource_task_idrequiredpoll_interval_ms

text_to_video

Create a Veo 3.1 task on RunAPI (text to video). Returns a task id, status, and output URLs.

Parameterswaitmodelseedspromptwatermarkinput_modetimeout_msaspect_ratiocallback_urlduration_secondspoll_interval_msenable_translation+3 more

upscale_video

Create a Veo 3.1 task on RunAPI (upscale video). Returns a task id, status, and output URLs.

Parameterswaitindextimeout_mscallback_urlsource_task_idpoll_interval_msoutput_resolution

get_task

Fetch the current status and latest result payload for a veo-3-1 task.

Parametersactionrequiredtask_idrequired

check_pricing

Look up RunAPI pricing for the veo-3-1 model line.

Parametersmodelaction

Version history

3
  1. v0.2.1LatestOct 22, 2026
  2. v0.2.0Sep 30, 2026
  3. v0.1.10Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts