Motion, in your agent’s toolkit.
Connect a Streamable HTTP MCP client to https://YOUR_ORIGIN/api/mcp with your API key as a Bearer header. Client support for custom headers is required; OAuth discovery is not implemented.
{
"mcpServers": {
"motionai": {
"type": "http",
"url": "https://YOUR_ORIGIN/api/mcp",
"headers": {"Authorization":"Bearer <YOUR_KEY>"}
}
}
}Available tools
Scene work: list_templates, list_skills, list_projects, create_project, get_project, save_project, generate_motion and get_job.
Full design: list_design_skills, list_design_conversations, create_design_conversation, ask_design_agent, get_design_conversation, get_design_history, resume_design_agent, cancel_design_agent and delete_design_conversation.
Rendering: get_render_config, create_render, get_render, cancel_render and retry_render. Learning: list_design_learningand forget_design_learning.
Complete a review safely
A paused conversation contains the exact actions needing review. Present those actions and any separate render cost to the user before calling resume_design_agent. Do not send another paid message to approve an existing request. Reuse the same idempotency key after an uncertain network response. Background follow-ups are off unless the user explicitly authorizes them.
The motionai://skills resource exposes the skill catalog. The motion-brief prompt helps write a structured brief. Ask for user agreement before spending generation credits.