← Ahmad Bilto

Unity editor tool

NAV MCP

One external server that connects automation clients to every Unity Editor I have open.

Drives every open Unity Editor from one external MCP server: 92 operations behind six tools, a 910-token idle surface, main-thread batching, and mirrored scene reads.

Overview

A flat Unity MCP catalog can charge an automation client for hundreds of tool schemas before it has done any work, while every live Editor call still has to wait for Unity's main thread. The server NAV MCP replaces exposed 356 tools at roughly 56,800 tokens and paid that context cost on every turn.

NAV MCP moves the durable state outside Unity into one .NET daemon, puts 92 Editor operations behind six MCP tools, and drives every linked Editor from the same desktop app. Guidance and schemas load only when needed; scene reads come from a live mirror; mutations batch into one Editor tick and one undo group.