MYEQ MCP overview
MCP exposes semantic production tools over the same MYEQ server authority used by Studio and the HTTP API.
The public documentation is shareable, but API and MCP capability availability is governed by the live product manifest and account access. Foundation or experimental operations are not stability promises.
MCP is a transport, not a second product
The MCP client never becomes the source of truth. MYEQ validates project access, plans, costs, confirmation, idempotency, execution and receipts on the server.
Host-independent by design
The stdio server can be used from Claude-family clients, OpenAI-compatible MCP hosts and custom enterprise clients. The host may reason differently; MYEQ production authority does not.
Eight user languages, English technical schema
Tool names, fields and schemas remain English for interoperability. sourceLanguage, responseLanguage, dialogueLanguage, subtitleLanguage and visualPromptLanguage are independent production choices.
Do not embed large media in MCP JSON
Upload or register authorized assets through MYEQ, then pass durable asset identifiers. This keeps messages bounded and preserves storage, ownership and provenance rules.