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

ToolDescription
vmeg_list_materialsList uploaded video/audio materials in your project.
vmeg_delete_materialDelete an uploaded material. Requires explicit user confirmation.

Voices

ToolDescription
vmeg_list_basic_voicesList system voices. Filter by locale (e.g. en-US, zh-CN).
vmeg_list_clone_voicesList cloned voices in your project.

Create tasks

ToolDescription
vmeg_create_video_translation_taskCreate a video or audio translation task. Requires targetLanguage and one media source.
vmeg_create_subtitle_translation_taskCreate a subtitle translation task. Requires targetLanguage and one media source.

Tasks

ToolDescription
vmeg_list_tasksList recent tasks or poll a single task by taskId.
vmeg_delete_taskDelete a task. Requires explicit user confirmation.

Task draft (editor)

ToolDescription
vmeg_query_task_scriptsQuery translated script lines.
vmeg_query_task_subtitlesQuery subtitle clips.
vmeg_query_task_asrQuery ASR / original recognition lines.
vmeg_query_task_speakersQuery speakers and voice assignments.
vmeg_query_task_tracksQuery audio/video track blocks.
vmeg_save_task_draftApply draft edits. Does not auto re-translate or export.
vmeg_compose_task_draftRender/export a new video or audio from the saved draft.

Async follow-up

ToolDescription
vmeg_retranslate_task_scriptsRe-translate all scripts for an existing task.
vmeg_get_retranslate_statusPoll re-translation status.
vmeg_trigger_video_translation_all_ttsRe-dub all or selected scripts.
vmeg_get_tts_statusPoll per-script TTS dubbing status.

Upload (HTTP)

EndpointDescription
POST /api/mcp/material/uploadMultipart upload for local files. Returns materialId for create-task tools.

Media sources

Each create-task call needs exactly one source:
SourceWhen to use
materialIdFile already in your project (from upload or library)
sourceUrlHTTPS direct link — e.g. an agent attachment URL
youtubeUrlYouTube video URL only
For sourceUrl, pass a public HTTPS file URL. For local files, upload via POST /api/mcp/material/upload first.

Supported products

AgentManual custom MCPVMEG authStatus
CursorYes — mcp.json or SettingsAPI Key (Bearer)Available
ClaudeYes — Add custom connectorOAuth on ConnectAvailable
Claude CodeYes — claude mcp addAPI Key or OAuthAvailable
Gemini CLIYes — settings.jsonAPI Key (Bearer)Available
ManusYes — Custom MCP connectorAPI Key (Bearer only)Available
ChatGPTNoComing soon
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:
https://www.vmeg.ai/api/mcp

Remote MCP

Remote MCP
SetupManual MCP URL + API Key
Runs onVMEG hosted infrastructure
AuthenticationOAuth or API Key
BillingYour existing VMEG plan credits
Best forAny MCP-compatible agent

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).