vmeg_*). Unless noted, do not pass projId — the authenticated OAuth session or API Key supplies the project.
Field-level JSON schemas are returned by the MCP
tools/list response. This page summarizes names and behavior. REST equivalents (where they exist) live in API reference.Materials
HTTP upload (not an MCP tool):
POST {mcpMaterialUploadUrl} with multipart/form-data file field. Returns materialId for create-task tools.
Voices
Tasks — create and manage
Tasks — editor queries
All query tools taketaskId and optional filters. Times are on the post-translation timeline unless noted.
Tasks — editor mutations
Agent behavior (server instructions)
The MCP server injects instructions for connected clients. Highlights:- Never pass
projIdin tool arguments. - Do not call create-task tools without a media source — ask how the user wants to provide media first.
- Confirm before delete, compose, re-translate, or bulk TTS.
- Tasks are asynchronous; poll
vmeg_list_tasksand editor query tools until work completes.
OAuth challenge
If a tool is called without a valid Bearer token, the server returns an MCP error with_meta OAuth challenge headers so clients (e.g. ChatGPT Apps SDK) can start login. After authorization, retry the tool call.
