Connector URL
https://videogenapi.com/mcp
Landing page and protocol share this URL. Browsers get the setup guide; agents POST JSON-RPC over Streamable HTTP.
Authentication
OAuth 2.1 + PKCE. Claude custom connectors register dynamically, open the consent screen, and store a Bearer token. Discovery:
/.well-known/oauth-protected-resource/.well-known/oauth-authorization-server
Personal token from Dashboard → MCP. Send Authorization: Bearer vgmcp_….
REST API keys also work as Bearer tokens on the MCP endpoint, so existing integrations can attach without a second secret.
Cursor example
{ "mcpServers": { "videogenapi": { "url": "https://videogenapi.com/mcp", "headers": { "Authorization": "Bearer vgmcp_YOUR_TOKEN" } } } }
Claude Code: add "type": "http" next to the URL. Tokens are created in Dashboard → MCP.
Tools
| Tool | What it does |
|---|---|
| get_account | Plan, remaining generations, balance |
| list_models | sora-2, veo3, kling-3, grok-imagine, seedance-2 and limits |
| generate_text_to_video | Prompt → job. Args: prompt, model, duration, aspect_ratio, resolution |
| generate_image_to_video | HTTPS image URL + motion prompt → job |
| get_video_status | Poll a generation_id until completed |
| list_videos | Recent generations on this account |
Jobs are asynchronous. After generate_*, poll get_video_status and share video_url when status is completed.
Plans & limits
MCP generations use your VideoGenAPI subscription, monthly quota and the same rate limiter as POST /v1/generate.
Insufficient quota or a paused subscription return a tool error the agent can show to the user.
There is no extra MCP fee.
Visual setup guide: videogenapi.com/mcp