Skip to main content
Connect VMEG to an MCP-compatible AI agent and translate video, audio, or subtitles through conversation — no custom integration code required. Usage draws on your existing VMEG plan credits.
App marketplace / one-click connectors are not supported yet. Use manual setup below with an API Key.

Add VMEG to your agent (manual)

1

Get an API Key

Create a key on API Configuration. You need a paid plan with credits — see Pricing.
2

Add a custom MCP server

In your MCP-compatible agent, open Connectors or MCP servers and choose Add custom connector (not a marketplace listing).
3

Enter the endpoint and Bearer token

  • Name: VMEG
  • URL: https://www.vmeg.ai/api/mcp
  • Authorization: Bearer YOUR_API_KEY
4

Start translating

Ask your agent to translate media — for example, “Translate this video to Spanish with VMEG.” The agent calls VMEG tools and bills against your plan.
Per-agent steps: Cursor, Claude, and others in Supported products. ChatGPT is coming soon.

What you can do

Once connected, your AI agent has access to the following tools:

Materials

Voices

Create tasks

Tasks

Task draft (editor)

Async follow-up

Upload (HTTP)

Media sources

Each create-task call needs exactly one source: For sourceUrl, pass a public HTTPS file URL. For local files, upload via POST /api/mcp/material/upload first.

Supported products

Setup guides for each manual-capable agent are linked above. App marketplace one-click install is listed at the bottom of each guide as coming soon. Any other MCP-compatible client can use the same endpoint:

Remote MCP

App marketplace

One-click installs from marketplaces or app stores are not supported yet. ChatGPT support is coming soon. For agents that support manual MCP, use manual setup with your API Key.

FAQ

For manual setup, yes — create an API Key and send it as Authorization: Bearer on MCP requests. Some future marketplace connectors may use OAuth instead.
No. Translation uses credits included in your VMEG plan. See Pricing.
Free and paid VMEG accounts can connect MCP. Submitting translation tasks deducts credits from your account as usual — see Pricing.
Yes. MCP binds to your VMEG project (via API Key or OAuth) and uses the same materials, tasks, and project resources as the website.
No. Materials, tasks, and voiceId values created through the Open API are separate from MCP. Do not mix IDs across the two channels. See API assets.
MCP exposes translation tools for AI agents (OAuth, VMEG project scope, shared with the web app). The Open API exposes REST endpoints for programmatic backends (API Key, separate asset store).