$ loading_
Control the Unity Editor from MCP hosts via a local Rust server bridge.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "Patina Unity MCP" MCP server from askskill: Run: claude mcp add 'io-github-taygunsavas-patina-unity-mcp' -- npx -y com.taygunsavas.patina-unity-mcp
Use Patina Unity MCP to connect to my local Unity Editor and perform a basic control action. If prerequisites are needed, list them first.
Returns the connection/control result, or explains prerequisites such as the local Rust server and C# Unity bridge.
I want to integrate Patina Unity MCP into my workflow. Based on the known information, summarize its components, how it operates, and the environment prerequisites I should verify.
Explains that the tool controls the Unity Editor through a local Rust server and a C# Unity bridge, and notes that detailed setup steps require checking the source repository.
Assess whether Patina Unity MCP is suitable for automating Unity Editor actions from an AI or MCP host, and describe the known capability boundaries.
States that it is suitable for MCP-based Unity Editor control, but the exact supported editor actions are not specified in the available information.
Developers using MCP-capable hosts can use this tool to send commands to a local Unity Editor. It fits scenarios where Unity Editor control needs to be triggered from an external workflow.
When a team wants to connect an MCP host with Unity through a local service, this tool provides a Rust server plus a C# Unity bridge architecture. It is suitable for local integration and prototyping.
It is an MCP tool that controls the Unity Editor from MCP hosts through a local Rust server and a C# Unity bridge.
Based on the available information, it at least involves a local Rust service, a C# bridge on the Unity side, and an MCP host that can connect to it. For exact installation steps and version requirements, see the source repository.
The known difference is that it is designed for control from MCP hosts and uses a local Rust server plus a C# bridge for integration. For more feature-level differences, the available information is insufficient; see the source repository.
Connect AI to Unity Editor for assets, scenes, scripts, and automation.
Connect AI to the Unity Editor for interaction, debugging, and automation.
Let AI query and control the Unity Editor for scene and asset tasks.
Connect to a local Unity Editor MCP server for AI-driven development tasks.
Connect Unity Editor with AI coding assistants for faster development and debugging.
Connect AI assistants to Unity Editor for project interaction and extensible development.