Unity-AI-Animation

Unity AI Animation is an asset that provides AI-powered tooling to create and modify AnimationClips and AnimatorControllers directly from natural language commands within Unity. When integrated with an MCP-compatible workflow, you can leverage the server to process prompts and return structured actions for Unity to execute, enabling automated setup of state machines, transitions, and keyframes. Typical usage involves sending a request describing the desired animation workflow (e.g., create a state machine with a walk cycle, add a transition with a parameter, or generate keyframes for a jump) and receiving actionable results that Unity can apply to assets or animator controllers. This MCP-backed approach helps accelerate prototyping and procedurally generated animation pipelines by combining natural language input with Unity’s animation tooling.

Prerequisites:

• Unity installed (supported versions per project needs)
• Docker installed and running (for the docker-based MCP server example below)
• Basic familiarity with Unity Asset installation and OpenUPM/OpenUPM-CLI if you opt to install via package managers

Option A: Docker-based MCP server (recommended for isolated environments)

1. Ensure Docker is running on your machine.
2. Pull and run the Unity AI Animation MCP image: docker run -it ivanmurzak/unity-ai-animation
3. Follow the container's output to connect your MCP client to the Unity AI Animation server.

Option B: OpenUPM integration (Unity package management within a project)

1. Open Unity and your project.
2. Install OpenUPM CLI if not already installed: https://github.com/openupm/openupm-cli#installation
3. From the project folder, install the package via: openupm add com.ivanmurzak.unity.mcp.animation
4. Use the Unity Editor to access the AI Animation tools and connect to your MCP server as described by the documentation.

Option C: Local development (if you are building or debugging the MCP integration)

1. Clone the Unity AI Animation repository.
2. Set up your Unity project to reference the asset locally or via the OpenUPM package.
3. Run the MCP client configuration to point at your server (see mcp_config example).

Tips and considerations:

• The MCP server configuration shown uses a Docker image name; replace with the actual image you maintain or use. Ensure network access between your MCP client and the server.
• If Unity assets rely on specific Unity versions, align the MCP workflow with supported Unity versions listed by the asset (as per release notes).
• When using OpenUPM, ensure you have the correct package name (com.ivanmurzak.unity.mcp.animation) and that the package is compatible with your Unity version.
• Environment variables for the MCP server (if any) should include authentication or endpoint configuration as required by your setup. For Docker runs, you may also need volume mappings or port configuration depending on your client.
• Common issues: networking between Docker containers and host, Unity asset import failures, and mismatches between Unity version and asset compatibility. Check logs from the Docker container or MCP client for troubleshooting hints.