The loop that matters is refresh, read the console, run the tests - an assistant editing C# can now see what Unity made of its change instead of asking you. Because the tool layer is C# inside the project, project-specific tools are yours to add.
An MCP server that lives inside the Unity Editor as a Unity package and serves Streamable HTTP. Its tools are written in C# with the MCP C# SDK, so a project can add its own; a Node relay covers clients that only speak stdio. The project describes itself as in preview.
- Unity Editor assets refreshed
- The current console logs read back, and the console cleared
- Edit mode tests run, and play mode tests run
- Extended tools written entirely in C# inside your own project
- Streamable HTTP directly, or stdio through the relay for clients that need it
Unity, with the server added to the project as a package. Node is needed only when your client does not speak Streamable HTTP and has to go through the stdio relay.
One command — claude mcp add -s project --transport http unity-natural-mcp http://localhost:56780/mcp