V4V – AI Video Generation

Crie vídeos com IA a partir do Claude, ChatGPT ou Codex: cole um link de produto para obter um anúncio pronto no Studio, execute mais de 30 modelos de vídeo (Veo 3.1, Seedance, Kling, Gemini Omni), edite em uma linha do tempo e veja o custo em créditos antes de cada execução. O Video Editor também está disponível: edite seus vídeos pelo nosso servidor, sem precisar instalar nada.

Servidor MCP hospedado

npx add-mcp 'https://v4v.ai/api/mcp'

Instala no Claude Code, Codex, Cursor e outros

Documentação

Create from your AI assistant.

Sign in with OAuth 2.1 or connect with an API key. Discover models, create with reference media, assemble multi-layer edits, and bring finished video, images and audio into your conversation.

ENDPOINT https://v4v.ai/api/mcp

{
  "type": "http",
  "url": "https://v4v.ai/api/mcp"
}

01

Connect your assistant

For guided setup, choose your assistant on the MCP connection page.

V4V MCP lets an AI assistant discover generation models, work with reference media, create images, video, audio and chat responses, and retrieve results. It uses the same account, credits and generation history as the V4V API.

Server URL: https://v4v.ai/api/mcp

Transport: Streamable HTTP

Authentication: OAuth 2.1 sign-in on enabled deployments, or an API key in clients that support custom request headers. Both use your existing V4V account and credits.

Use your deployment's domain in place of v4v.ai when testing another environment. The server is already hosted; you do not need to run a local process.

Sign in with OAuth

Choose this option in ChatGPT, Claude, or a supported editor or CLI. You do not need to create an API key. Add the remote server URL, select OAuth / Sign in, and complete the V4V permission screen. See OAuth authorization and the client-specific steps below.

Connect with an API key

  1. Open your V4V profile and create a key under API Keys.
  2. Save the API secret in your MCP client's secure settings.
  3. Add the server with x-api-key: YOUR_V4V_API_KEY or Authorization: Bearer YOUR_V4V_API_KEY.
  4. Connect and start with get_balance or list_models.

Send one authentication header. If both are sent, they must contain the same key; conflicting or malformed credentials return HTTP 401. The x-api-key value is the key itself, without a Bearer prefix. Both API-key header formats use the same permissions, credits, rate limits and key revocation.

API-key clients continue to use the same headers and permissions. OAuth clients sign in to their existing V4V account through the browser. Never paste a key or token into an assistant conversation or commit it to a repository.

02

OAuth 2.1 authorization

  1. Add https://v4v.ai/api/mcp as a remote server in your assistant.