Question 1

Why do some clients fail with KeyError: 'position' during tool initialization?

Accepted Answer

Some MCP clients may fail while parsing tool schemas when they contain local JSON pointer references such as #/properties/position. MCP Unity avoids this by registering transform tool inputs (set_transform, move_gameobject, rotate_gameobject, scale_gameobject) with fresh nested vector schemas per field, so the generated schema does not rely on local #/properties/... references. If you still see this error: update your MCP client to the latest version, rebuild the Node server (cd Server~ && npm run build), confirm your package version includes this compatibility fix.

Question 2

Why do I get a connection failed error when running Play Mode tests?

Accepted Answer

The run_tests tool returns the following response: Error: Connection failed: Unknown error This error occurs because the bridge connection is lost when the domain reloads upon switching to Play Mode. The workaround is to turn off Reload Domain in Edit > Project Settings > Editor > "Enter Play Mode Settings".

Question 3

Why won't the MCP Unity server start?

Accepted Answer

Check the Unity Console for error messages Ensure Node.js is properly installed and accessible in your PATH Verify that all dependencies are installed in the Server directory

Question 4

Why am I unable to connect to MCP Unity?

Accepted Answer

Ensure the WebSocket server is running (check the Server Window in Unity) Send a console log message from MCP client to force a reconnection between MCP client and Unity server Change the port number in the Unity Editor MCP Server window. (Tools > MCP Unity > Server Window)

Question 5

Is MCP Unity free to use?

Accepted Answer

Yes, MCP Unity is an open-source project distributed under the MIT License. You are free to use, modify, and distribute it according to the license terms.

Question 6

Can I extend MCP Unity with custom tools for my project?

Accepted Answer

Yes, absolutely! One of the significant benefits of the MCP Unity architecture is its extensibility. In Unity (C#): You can create new C# classes that inherit from McpToolBase (or a similar base for resources) to expose custom Unity Editor functionality. These tools would then be registered in McpUnityServer.cs. For example, you could write a tool to automate a specific asset import pipeline unique to your project. In Node.js Server (TypeScript): You would then define the corresponding TypeScript tool handler in the Server/src/tools/ directory, including its Zod schema for inputs/outputs, and register it in Server/src/index.ts. This Node.js part will forward the request to your new C# tool in Unity. This allows you to tailor the AI's capabilities to the specific needs and workflows of your game or application.

Question 7

What MCP hosts and IDEs currently support MCP Unity?

Accepted Answer

MCP Unity is designed to work with any AI assistant or development environment that can act as an MCP client. The ecosystem is growing, but current known integrations or compatible platforms include: Cursor Windsurf Claude Desktop Claude Code Codex CLI GitHub Copilot Google Antigravity OpenCode

Question 8

What is MCP Unity?

Accepted Answer

MCP Unity is a powerful bridge that connects your Unity Editor environment to AI assistants LLM tools using the Model Context Protocol (MCP). In essence, MCP Unity: Exposes Unity Editor functionalities (like creating objects, modifying components, running tests, etc.) as "tools" and "resources" that an AI can understand and use. Runs a WebSocket server inside Unity and a Node.js server (acting as a WebSocket client to Unity) that implements the MCP. This allows AI assistants to send commands to Unity and receive information back. Enables you to use natural language prompts with your AI assistant to perform complex tasks within your Unity project, significantly speeding up development workflows.

Question 9

How does MCP Unity compare with the upcoming Unity 6.2 AI features?

Accepted Answer

Unity 6.2 is set to introduce new built-in AI tools, including the previous Unity Muse (for generative AI capabilities like texture and animation generation) and Unity Sentis (for running neural networks in Unity runtime). As Unity 6.2 is not yet fully released, this comparison is based on publicly available information and anticipated functionalities: Focus: MCP Unity: Primarily focuses on Editor automation and interaction. It allows external AI (like LLM-based coding assistants) to control and query the Unity Editor itself to manipulate scenes, assets, and project settings. It's about augmenting the developer's workflow within the Editor. Unity 6.2 AI: Aims at in-Editor content creation (generating textures, sprites, animations, behaviors, scripts) and AI-powered assistance for common tasks, directly integrated into the Unity Editor interface. A fine-tuned model to ask any question about Unity's documentation and API structure, with customized examples more accurate to Unity's environment. Adds the functionality to run AI model inference, allowing developers to deploy and run pre-trained neural networks within your game or application for features like NPC behavior, image recognition, etc. Use Cases: MCP Unity: "Create a new 3D object, name it 'Player', add a Rigidbody, and set its mass to 10." "Run all Play Mode tests." "Ask to fix the error on the console log." "Execute the custom menu item 'Prepare build for iOS' and fix any errors that may occur." Unity 6.2 AI: "Generat

Question 10

Why use MCP Unity?

Accepted Answer

MCP Unity offers several compelling advantages for developers, artists, and project managers: Accelerated Development: Automate repetitive tasks, generate boilerplate code, and manage assets using AI prompts. This frees up your time to focus on creative and complex problem-solving. Enhanced Productivity: Interact with Unity Editor features without needing to manually click through menus or write scripts for simple operations. Your AI assistant becomes a direct extension of your capabilities within Unity. Improved Accessibility: Allows users who are less familiar with the deep intricacies of the Unity Editor or C# scripting to still make meaningful contributions and modifications to a project through AI guidance. Seamless Integration: Designed to work with various AI assistants and IDEs that support MCP, providing a consistent way to leverage AI across your development toolkit. Extensibility: The protocol and the toolset can be expanded. You can define new tools and resources to expose more of your project-specific or Unity's functionality to AI. Collaborative Potential: Facilitates a new way of collaborating where AI can assist in tasks traditionally done by team members, or help in onboarding new developers by guiding them through project structures and operations.

نظرة عامة

الميزات الرئيسية

التسعير

حالات الاستخدام

تطوير الألعاب

البرمجة المدعومة بالذكاء الاصطناعي

المزايا والعيوب

المزايا

العيوب

المراجعات

أسئلة وأجوبة

اطرح سؤالاً

بدائل لـ مضيفي MCP

Playwright MCP

Pydantic AI

Cognee

Inbox Zero

Screenpipe

AgentKit

onchain-mcp

markitdown