Manual setup (recommended)
1
Get an API Key
Create a key on API Configuration (sign in if needed). You need a paid plan with credits — see Pricing.
2
Add the MCP server
In your MCP client, add a custom / remote MCP server (not a marketplace listing):
- URL:
{mcpUrl} - Auth:
Authorization: Bearer YOUR_API_KEY(use the key from API Configuration)
3
Reload the client
Restart or reload your editor so the new MCP server is picked up.
4
Verify
Ask the agent to list materials (for example: “List my VMEG materials”). It should call
vmeg_list_materials.Cursor example
Add to your project or user MCP config (.cursor/mcp.json):
Other MCP clients
Any client that supports Streamable HTTP remote MCP can use the same values:
The API Key binds to one VMEG project — the same scope as Open API. You do not pass
projId in tool arguments.
Material upload (HTTP)
Create-task tools acceptmaterialId, sourceUrl, or youtubeUrl. To upload a file before creating a task:
data.id is the materialId for vmeg_create_video_translation_task or vmeg_create_subtitle_translation_task.
OAuth (connectors, advanced)
VMEG also exposes OAuth 2.1 (PKCE) for clients that cannot embed an API Key (for example, future ChatGPT Apps / Connector flows). This path is not required for manual setup above.
Resolved issuer for tokens:
{mcpOAuthUrl}.
Marketplace and app-store connectors
Not supported yet. Do not rely on Cursor marketplace listings or ChatGPT Connector one-click install until VMEG publishes them. Use manual setup with your API Key instead. When marketplace support ships, this page will add product-specific steps. Until then, only custom / remote MCP configuration is documented.Troubleshooting
See Error codes for Open API-style failures surfaced through tools.

