Unity MCP Template

What is Unity MCP Template?

Unity MCP Template is a simple example project that demonstrates interaction between a TypeScript‑based MCP server and Unity. It serves as a starting point for developers to build and configure their own tools that bridge an MCP client (e.g., Claude Desktop) with the Unity editor.

How to use Unity MCP Template?

Clone the repository, navigate to unity-mcp-server, run npm install and npm run build. Then add the built server to Claude Desktop via its Developer‑Edit Config, pointing to the generated index.js file. Open the Unity project and manage the MCP through the “UnityMCP‑ShowWindow” menu item at the top.

Key features of Unity MCP Template

• Pre‑configured TypeScript MCP server for Unity
• Unity EditorWindow implemented with IMGUI
• No dependency on NewtonsoftJSON for broader compatibility
• Example tool (CreateObjectTool) to easily extend
• Ready‑to‑use integration with Claude Desktop
• Open‑source and MIT licensed

Use cases of Unity MCP Template

• Prototype an AI‑assisted Unity editor tool that creates objects via natural language
• Build custom MCP tools for automating repetitive Unity tasks (e.g., scene setup)
• Learn how to connect an MCP server to a game engine for interactive workflows

FAQ from Unity MCP Template

What is the purpose of Unity MCP Template?

It is a minimal example that shows how an MCP server can communicate with Unity. You can use it as a base to create your own Unity‑MCP tools.

How do I add the server to Claude Desktop?

Open Claude Desktop Settings, go to Developer‑Edit Config, and add a JSON entry with the command node and the full path to the compiled index.js file.

How can I create custom tools in this template?

In Unity, reference the existing CreateObjectTools class. In TypeScript, reference the createObject function. Both sides must use the same input data structure.

What are the runtime requirements?

Node.js and npm are required to build and run the TypeScript MCP server. Unity (any version, no NewtonsoftJSON needed) is needed for the example project.

Does the server use a specific transport?

The current implementation uses TCP (with roles reversed due to a TypeScript SDK issue). The TODO list indicates a planned change to a standard client‑server TCP structure.