The scoping is the thing to get right on day one: media generation and the coding API are separate products with separate keys, and using the wrong one reads as an auth failure rather than a permissions message. For media work the hosted MCP endpoint is the shortest path; the bundled proxy exists for clients that cannot attach an Authorization header, which is still a common gap.
The public discovery surface for VAP AI's Media API and its MCP endpoint. The Media API is a single generation interface across image, video and music workflows; the MCP endpoint puts that interface in front of any MCP client, so generation becomes a tool call rather than an HTTP integration.
- Image, video and music generation through one unified API surface
- Current public model surfaces named as Pimo AI-Video, Aura Image Turbo and Pira V5.5
- A hosted MCP endpoint at `https://api.vapagent.com/mcp`, authorised with a product-scoped VAP Media API key
- A local stdio and HTTP proxy at `mcp/vap_mcp_proxy.py` for clients that cannot send custom headers
- The same account also carries a separate Coding Plan API — an OpenAI-compatible surface with model ID `vap-code` — for coding agents and editors
A VAP account and a product-scoped Media API key, generated from the Developer Hub. The MCP endpoint takes the key as an `Authorization: Bearer` header, which is straightforward in Claude Desktop and Cursor-compatible clients; where headers are not supported, run the bundled proxy and set `VAP_API_KEY` instead. The Media API base is `https://api.vapagent.com/api/v1`, with generation and operation endpoints under it. Keys are scoped per product, so a Media key does not unlock the Coding Plan API.
One command plus a key — npx -y mcp-remote https://api.vapagent.com/mcp, then supply credentials