RefreshAssetsLABSCO SUMMARY
The editor answers, so the agent stops guessing whether the build compiled.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Follow the published steps
USE CASES
01
Finding out whether the change compiled
Refresh the assets and read the console back, so a compile error surfaces in the same turn that wrote the code.
02
Running the test suite from the chat
Run edit mode and play mode tests directly, and read the results without switching to the editor window.
03
Reading an error the editor threw
Pull the current console logs, then clear them so the next run starts from a clean slate.
04
Getting a clean signal after a noisy session
Clear the console, refresh, and read only what the new state produced.
5 tools
Listed in project docs. Your client may show a different list.
GetCurrentConsoleLogsClearConsoleLogsRunEditModeTestsRunPlayModeTestsBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- A client that can reach a remote MCP server over HTTP
- Node.js 18.0.0 or later
- Unity 6000.0 or later
- UniTask
- NugetForUnity
- NuGet packages System.Text.Json 9.0.x, ModelContextProtocol 0.2.x, Microsoft.Extensions.DependencyInjection 9.0.x
Where it runs
All 4 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
Install the dependencies first: UniTask, NugetForUnity, then via NugetForUnity the NuGet packages System.Text.Json 9.0.x, ModelContextProtocol 0.2.x (enable the Show Prerelease toggle) and Microsoft.Extensions.DependencyInjection 9.0.x
Edit Packages/manifest.json and add to the dependencies section: "jp.notargs.unity-natural-mcp": "https://github.com/notargs/UnityNaturalMCP.git?path=/UnityNaturalMCPServer"
Open Edit > Project Settings > Unity Natural MCP, set the MCP server port number (default: 56780), click Refresh
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add -s project --transport http unity-natural-mcp http://localhost:56780/mcpVS Code
VS CODE · JSON
{
"servers": {
"unity-natural-mcp": {
"url": "http://localhost:56780/mcp"
}
}
}Cursor
Please download the latest mcp-stdio-to-streamable-http from mcp-stdio-to-streamable-http Releases.
CURSOR · JSON
{
"mcpServers": {
"unity-natural-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_STDIO_TO_STREAMABLE>/dist/index.js"
],
"env": {
"MCP_SERVER_IP": "localhost",
"MCP_SERVER_PORT": "56780"
}
}
}
}Gemini CLI
GEMINI CLI · JSON
{
"mcpServers": {
"httpServer": {
"httpUrl": "http://localhost:56780/mcp"
}
}
}
