MCP setup, tools and safety
Configure the stdio server once, discover capabilities, plan for free and confirm paid execution explicitly.
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.
| Tool | Authority | Purpose | Automatic retry |
|---|---|---|---|
| myeq.capabilities.search | read | Discover production capabilities | 429 / 502 / 503 |
| myeq.production.plan | plan | Compile a free, inspectable plan | never |
| myeq.production.preflight | read | Validate readiness and estimated cost | 429 / 502 / 503 |
| myeq.storyboard.apply | mutate | Apply an approved Storyboard | never |
| myeq.production.execute_step | spend | Execute one confirmed plan step | never |
| myeq.production.execute | spend | Start confirmed durable production | never |
| myeq.job.status | read | Read durable job progress | 429 / 502 / 503 |
| myeq.production.ledger | read | Read the owner-scoped execution ledger | 429 / 502 / 503 |
| myeq.production.verticals | read | List production recipes | 429 / 502 / 503 |
Generic stdio configuration
Build the MCP package, provide MYEQ_API_KEY and MYEQ_BASE_URL, then point your MCP host at the stable server entrypoint. Client-specific screens may differ.
{
"mcpServers": {
"myeq": {
"command": "node",
"args": ["/absolute/path/to/myeq-full/mcp/dist/server.js"],
"env": {
"MYEQ_API_KEY": "your-key",
"MYEQ_BASE_URL": "https://myeq.pro"
}
}
}
}Start with discovery and planning
Search capabilities before assuming a feature. Create an inspectable plan, preflight it, then apply Storyboard or execute only after the user has authorized the mutation or spend.
{
"projectId": "project-123",
"instruction": "Create a 60-second vertical trailer",
"vertical": "ai_film",
"sourceLanguage": "en",
"responseLanguage": "es",
"dialogueLanguage": "es",
"visualPromptLanguage": "en"
}Never blind-retry paid tools
Paid tools require confirm=true and an idempotency key. A successfully accepted durable job remains owned by MYEQ even if the MCP client disconnects.
Resume by job identity
Long-running execution returns a durable job identifier. Reconnect later and read job status; do not depend on the chat, editor or terminal process remaining alive.