Skip to main content
ClaudeWave

RunAPI Veo 3.1 MCP server for video generation: create tasks, poll results, and check pricing across 3 model variants from Claude Code, Codex, Cursor, and VS Code.

MCP ServersRegistry oficial0 estrellas0 forksTypeScriptApache-2.0Actualizado today
Install in Claude Code / Claude Desktop
Method: NPX · @runapi.ai/veo-3-1-mcp
Claude Code CLI
claude mcp add veo-3-1-mcp -- npx -y @runapi.ai/veo-3-1-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "veo-3-1-mcp": {
      "command": "npx",
      "args": ["-y", "@runapi.ai/veo-3-1-mcp"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

<h1 align="center">RunAPI Veo 3.1 MCP Server</h1>

<p align="center">
  <strong>Veo 3.1 API access for AI agents: run video generation operations, poll asynchronous results, and check pricing through one focused MCP server.</strong>
</p>

<p align="center">
  <sub>Works with Claude Code, Codex, Cursor, Windsurf, VS Code, Roo Code, and any MCP-compatible host.</sub>
</p>

<p align="center">
  <a href="https://www.npmjs.com/package/@runapi.ai/veo-3-1-mcp"><img src="https://img.shields.io/npm/v/%40runapi.ai/veo-3-1-mcp?style=flat-square&color=blue" alt="npm version"></a>
  <a href="https://github.com/runapi-ai/veo-3-1-mcp"><img src="https://img.shields.io/badge/GitHub-runapi--ai%2Fveo--3--1--mcp-24292f?style=flat-square" alt="GitHub repository"></a>
  <a href="LICENSE"><img src="https://img.shields.io/badge/License-Apache_2.0-blue?style=flat-square" alt="Apache-2.0 license"></a>
  <img src="https://img.shields.io/badge/Type-MCP_Server-blue?style=flat-square" alt="MCP Server">
  <img src="https://img.shields.io/badge/Models-3-16a34a?style=flat-square" alt="3 models">
</p>

<p align="center">
  <a href="#install">Install</a> |
  <a href="#tools">Tools</a> |
  <a href="#models">Models</a> |
  <a href="#agent-prompts">Agent Prompts</a> |
  <a href="#configuration">Configuration</a> |
  <a href="#links">Links</a>
</p>

---

## 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`](https://github.com/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/`](examples/) for Claude, Cursor, Windsurf, VS Code, and Roo Code.

---

## Tools

| Tool | Auth | Purpose |
|---|---|---|
| `extend_video` | Yes | Create a Veo 3.1 extend video task and optionally wait for a terminal status. Returns the task id, status, output URLs, and pricing snapshot. |
| `text_to_video` | Yes | Create a Veo 3.1 text to video task and optionally wait for a terminal status. Returns the task id, status, output URLs, and pricing snapshot. |
| `upscale_video` | Yes | Create a Veo 3.1 upscale video task and optionally wait for a terminal status. Returns the task id, status, output URLs, and pricing snapshot. |
| `get_task` | Yes | Fetch the current status and latest payload for an existing task. |
| `check_pricing` | No | Look up the current pricing snapshot 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:

| Tool | Models |
|---|---|
| `extend_video` | _no model parameter_ |
| `text_to_video` | `veo-3.1`, `veo-3.1-fast`, `veo-3.1-lite` |
| `upscale_video` | _no model parameter_ |

Model availability can change between releases. Use `check_pricing` or the [Veo 3.1 model page](https://runapi.ai/models/veo-3.1) 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](https://runapi.ai/models/veo-3.1) 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

| Resource | URL |
|---|---|
| Veo 3.1 model page | [https://runapi.ai/models/veo-3.1](https://runapi.ai/models/veo-3.1) |
| npm package | [@runapi.ai/veo-3-1-mcp](https://www.npmjs.com/package/@runapi.ai/veo-3-1-mcp) |
| GitHub repository | [runapi-ai/veo-3-1-mcp](https://github.com/runapi-ai/veo-3-1-mcp) |
| RunAPI MCP overview | [runapi.ai/mcp](https://runapi.ai/mcp) |
| RunAPI docs | [runapi.ai/docs](https://runapi.ai/docs) |

---

## License

Licensed under the [Apache License, Version 2.0](LICENSE).
ai-agentsai-upscalingai-videoclaude-codecursorextend-videomcpmcp-servermodel-context-protocolrunapirunapi-aitext-to-videoupscale-videoveo-3-1veo-3-1-apiveo-3-1-mcpvideo-generationvscode

Lo que la gente pregunta sobre veo-3-1-mcp

¿Qué es runapi-ai/veo-3-1-mcp?

+

runapi-ai/veo-3-1-mcp es mcp servers para el ecosistema de Claude AI. RunAPI Veo 3.1 MCP server for video generation: create tasks, poll results, and check pricing across 3 model variants from Claude Code, Codex, Cursor, and VS Code. Tiene 0 estrellas en GitHub y se actualizó por última vez today.

¿Cómo se instala veo-3-1-mcp?

+

Puedes instalar veo-3-1-mcp clonando el repositorio (https://github.com/runapi-ai/veo-3-1-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar runapi-ai/veo-3-1-mcp?

+

runapi-ai/veo-3-1-mcp aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.

¿Quién mantiene runapi-ai/veo-3-1-mcp?

+

runapi-ai/veo-3-1-mcp es mantenido por runapi-ai. La última actividad registrada en GitHub es de today, con 0 issues abiertos.

¿Hay alternativas a veo-3-1-mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega veo-3-1-mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: runapi-ai/veo-3-1-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/runapi-ai-veo-3-1-mcp)](https://claudewave.com/repo/runapi-ai-veo-3-1-mcp)
<a href="https://claudewave.com/repo/runapi-ai-veo-3-1-mcp"><img src="https://claudewave.com/api/badge/runapi-ai-veo-3-1-mcp" alt="Featured on ClaudeWave: runapi-ai/veo-3-1-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a veo-3-1-mcp