motion-dev

Motion.dev MCP Server provides an offline-accessible Motion.dev animation library integration with comprehensive documentation, code generation, and multi-framework support. This server exposes a suite of tools to fetch documentation, search across docs, inspect component APIs, generate multi-animation components, convert code between React, JavaScript, and Vue, and validate syntax against the Motion.dev API. It is designed to run behind an MCP-compatible client and deliver fast, production-ready code and guidance for building animation-rich interfaces across React, JavaScript, and Vue projects.

Once the server is running, you can leverage the Documentation Access tools to retrieve motion.dev docs, perform full-text searches, view component APIs with practical examples, filter results by framework or category, and obtain framework-specific guides. For code-generation, you can assemble complex animations by combining patterns (e.g., scale and rotate) into reusable components, create intricate animation sequences, convert code across frameworks, validate syntax against the Motion.dev API, and receive optimization recommendations. The server supports advanced search (FTS5 with LIKE fallback), framework filtering, and rapid response times suitable for integration into AI-assisted development workflows.

Prerequisites:

• Node.js 18+ installed on your machine
• A MCP-compatible client to connect to the server

Installation steps:

1. Clone the repository:

git clone https://github.com/your-username/motion-dev-mcp.git
cd motion-dev-mcp

2. Install dependencies:

npm install

3. Build the TypeScript code:

npm run build

4. Initialize the documentation database (first time only):

npm run rebuild

5. Run the MCP server locally (example):

node dist/index.js

6. Optional: verify startup by querying the index or starting with a test client.

Configuration notes:

• If you need a custom database path or environment, set MOTION_DB_PATH or other recognized env vars before rebuilding.
• Ensure that your MCP client is configured to point at the motion-dev MCP server with the appropriate command and args.

Tips and common issues:

• Ensure Node.js 18+ is installed; older Node versions may fail to run the server.
• If the server fails to start, check that dist/index.js exists and that the build completed without errors.
• For Claude Code CLI or other MCP clients, use the provided mcpServers configuration block as a template to register the server.
• When upgrading, run npm run rebuild to refresh the offline documentation and code examples.
• Environment variables such as MOTION_DB_PATH can customize the location of the database; adjust accordingly before rebuilding.
• If you encounter slow searches, verify the SQLite index integrity and ensure the FTS5 extension is available in your runtime.
• The npm_package field is null for this Node.js MCP server since there isn’t a standard npm package name defined in the repository.