mcpField
V
Vap Agent images (Flux), videos (Veo 3.1), and music (Suno V5) media production

Vap Agent images (Flux), videos (Veo 3.1), and music (Suno V5) media production

Remote
vapagent.comMedia & Design1Updated 18w ago
RepositoryVisit website

About Vap Agent images (Flux), videos (Veo 3.1), and music (Suno V5) media production

VAP AI provides image, video, and music generation APIs for agent workflows, alongside a coding API. Its MCP endpoint lets compatible clients call media tools, with a local proxy available for clients that cannot send headers directly.

Key features

  1. 01Unified image, video, and music generation API
  2. 02Conversational AI Room creative workspace
  3. 03API for coding agents
  4. 04Media generation and operation endpoints
  5. 05Local MCP proxy

Use cases

  1. 01Generate media from MCP-compatible clients
  2. 02Create images, video, voice, and music in AI Room
  3. 03Connect the coding API to IDEs or automation workflows

MCP support

The remote MCP endpoint is https://api.vapagent.com/mcp, where Claude Desktop, Claude Code, Cursor-compatible clients, and other agent workflows can call media tools. Clients without direct header support can use the local proxy.

#developer-tools#image-generation#video-generation#music-generation#flux#veo#suno#ai-media#cost-control#mcp-server

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.vapagent.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://api.vapagent.com/mcpAuth required

Tools

16
ParameterTypeRequiredDescription
promptstringYesDetailed description of the image to generate. Note: If aspect ratio is mentioned in the prompt (e.g., '16:9', 'widescreen', 'portrait'), also pass it in the aspect_ratio parameter for guaranteed correct dimensions.
aspect_ratioenumNoOutput image aspect ratio. If the user mentions a specific ratio like '16:9' or 'widescreen' in their prompt, extract and pass it here explicitly for best results.1:1 | 16:9 | 9:16 | 4:3 | 3:4 | 3:2 | 2:3 | 21:9 | 9:21
qualityenumNoGeneration quality (high costs 1.5x)standard | high

Details

From the project README

VAP AI Saraswati emblem

VAP AI

Agent-native AI platform for AI Room, Media API, and Coding Plan API.

Website | Developer Hub | AI Room | Dashboard | Status

Products

AI Room

Conversational creative workspace where custom-trained AI agents use session context to create images, video, voice, and music.

Media API

Unified generation API for image, video, and music workflows. Current public model surfaces include Pimo AI-Video, Aura Image Turbo, and Pira V5.5.

  • Developer Hub: https://vapagent.com/developer/
  • API base URL: https://api.vapagent.com/api/v1
  • Create generation: POST /api/v1/generations
  • Create operation: POST /api/v1/operations
  • Authentication: product-scoped VAP Media API key
  • MCP endpoint: https://api.vapagent.com/mcp
Coding Plan API

OpenAI-compatible API for coding agents, IDEs, editors, and automation workflows. Powered by Nemesis Deep Coder with model ID vap-code.

Start From The Product Surface

Use these entry points for new integrations:

NeedLink
Use AI Roomhttps://vapagent.com/new
Generate a Media API keyhttps://vapagent.com/developer/?key=media#keys
Generate a Coding Plan API keyhttps://vapagent.com/developer/?key=code#keys
View Coding Plan API planshttps://vapagent.com/new-dashboard/?billing=code#plans
Read Developer Hubhttps://vapagent.com/developer/
See Nemesis Deep Coderhttps://vapagent.com/models/nemesis-deep-coder.html

Media API Via MCP

This repository remains the public GitHub and MCP discovery surface for VAP Media API integrations. MCP is still supported for Claude Desktop, Claude Code, Cursor-compatible MCP clients, and other agent workflows that call VAP media tools.

Claude Desktop example:

{
  "mcpServers": {
    "vap": {
      "url": "https://api.vapagent.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MEDIA_API_KEY"
      }
    }
  }
}

For clients that do not support headers directly, use the local proxy in mcp/vap_mcp_proxy.py and set VAP_API_KEY.

API Examples

Media API
curl -X POST https://api.vapagent.com/api/v1/generations \
  -H "Authorization: Bearer YOUR_MEDIA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"image","prompt":"a neon city at night"}'
Coding Plan API
curl -X POST https://api.vapagent.com/v1/chat/completions \
  -H "Authorization: Bearer YOUR_CODING_PLAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"vap-code","messages":[{"role":"user","content":"Review this patch."}]}'

Current Product Contracts

Use these current public contracts from Developer Hub:

  • Media API: https://api.vapagent.com/api/v1
  • Media generation: POST /api/v1/generations
  • Media operations: POST /api/v1/operations
  • MCP: https://api.vapagent.com/mcp
  • Coding Plan API: https://api.vapagent.com/v1

Discovery Files

  • server.json: MCP Registry server metadata
  • mcp.json: MCP package metadata
  • glama.json: Glama MCP listing metadata
  • mcp/tools.json: MCP tool schema metadata
  • mcp/vap_mcp_proxy.py: local stdio/http proxy for MCP clients

Links

License

MIT License. See LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.