DevMotion MCP Server
Connect AI assistants and automation platforms directly to DevMotion. Create projects, build animations, and manage layers through natural language — no API key required for interactive clients.
MCP Endpoint: https://devmotion.app/mcp
What is MCP?
The Model Context Protocol (MCP) is an open standard that lets AI clients interact with external tools and services. By connecting your AI client to DevMotion’s MCP server, the AI can create and edit animation projects on your behalf.
Who is this for?
| Use case | Recommended setup |
|---|---|
| Using Claude, Cursor, or Windsurf to animate | AI Coding Assistants → |
| Building automation workflows in n8n or Make | Enterprise & Automation → |
| Integrating with LangChain, CrewAI, or other AI frameworks | Enterprise & Automation → |
How it works
1. Connect — add DevMotion’s MCP endpoint to your client. The AI discovers available tools automatically.
2. Authenticate — sign in with your DevMotion account. Interactive clients (Claude, Cursor) handle OAuth automatically. Programmatic clients use a bearer token from your profile page.
3. Create — ask the AI to build an animation in plain language:
“Create a 1080×1920 TikTok intro with a bold title that slides in and a pulsing accent shape in the background.”
The AI calls create_project, create_layer, and edit_layer on your behalf. The result appears in your DevMotion editor instantly.
Authentication
DevMotion uses OAuth 2.0 built into the MCP protocol.
- Interactive clients (Claude Code, Claude Desktop, Cursor, Windsurf) — the OAuth flow runs automatically on first connection. No tokens to copy.
- Programmatic clients (n8n, LangChain, CrewAI, etc.) — obtain a long-lived token from your profile page and pass it as
Authorization: Bearer <token>.
Important: always use the same DevMotion account in your MCP client as in the browser. Projects and AI credits are tied to your account. See Plans & Limits for quota details.