Skip to main content
Today, connect VMEG Remote MCP by manually adding the server URL and your API Key. One-click marketplace or app-store connectors are not supported yet.
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): 
{
  "mcpServers": {
    "VMEG": {
      "url": "https://www.vmeg.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Reload Cursor (Cmd+Shift+P → Developer: Reload Window). In chat, confirm the VMEG MCP server is connected before calling tools.
Do not commit API Keys to git. Use environment-specific config or a local-only mcp.json entry.

​
Other MCP clients

Any client that supports Streamable HTTP remote MCP can use the same values:
FieldValue
Server URL{mcpUrl}
Authorization headerBearer YOUR_API_KEY
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 accept materialId, sourceUrl, or youtubeUrl. To upload a file before creating a task: 
curl -X POST "{mcpMaterialUploadUrl}" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "file=@/path/to/video.mp4"
The response 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.
EndpointPurpose
{mcpOAuthUrl}/.well-known/oauth-authorization-serverAuthorization server metadata
{mcpUrl}/.well-known/oauth-protected-resourceProtected resource metadata
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

SymptomWhat to check
MCP server not listedReload the client after editing mcp.json.
Tool returns auth errorAPI Key is valid and sent as Bearer on every MCP request.
vmeg_create_* fails with no mediaUpload, list materials, pass sourceUrl, or youtubeUrl first.
Wrong project dataCreate a new API Key under the intended project on API Configuration.
See Error codes for Open API-style failures surfaced through tools.