Unity-MCP: A Model Context Protocol for Unity Editor
Hey fellow devs!
I’ve been working on a tool for Unity Editor called Unity-MCP – it introduces a structured communication protocol between the Unity Editor and external tools like VS Code, local AI assistants, and more. Think of it as a flexible backend/server bridge designed specifically with editor tooling and live communication in mind.
GitHub: Unity-MCP – Apache 2.0 Licensed
What is Unity-MCP?
Unity-MCP is a protocol and tooling system that:
- Provides a context-aware RPC-style communication between the Unity Editor and external processes.
- Supports dynamic capabilities based on current Unity state.
- Enables building powerful AI-driven or scriptable editor extensions that can talk back-and-forth with Unity in real time.
Key Features:
Easy-to-extend protocol system (define your own handlers and models)
Works outside of Unity’s runtime – great for automation or desktop agents
Supports .NET clients, and can integrate with CLI tools or LLMs
Enables external control of the Unity Editor, like triggering actions, fetching data, and more
Use Cases:
- AI assistants for Unity (e.g., connect ChatGPT or Claude to automate repetitive editor tasks)
- Custom pipelines for data validation or project audits
- Real-time external debugger tooling
- VS Code / IDE extensions that reflect Unity’s current editor state
Tech Stack:
- C# server hosted in the Unity Editor (via UI Toolkit interface)
- Structured command-based protocol (Model + Context pattern)
- JSON-based communication over local TCP
Looking for Feedback:
I’m actively improving this and would love thoughts, feedback, or ideas for killer features. If anyone is building similar tooling or has thoughts on integrating LLMs with Unity – I’m all ears 
Also open to collaborators if this sparks any ideas!
Let me know what you think – would love to hear how this could be useful in your workflow or projects!
