MCP Tooling

The Model Context Protocol is a shared wire format for giving AI assistants access to external tools. Dynamo uses it to drive the Unity Editor through mcp-unity-plus.

mcp-unity-plus — the Unity Editor over MCP

Dynamo ships with mcp-unity-plus, a Unity Editor MCP server that gives the assistant direct control of the running editor. Install the companion unity-dynamo package in your Unity project, register the server in dynamo.yaml, and the full toolbox is available in chat:

• ●Scene operations — load, save, create, unload scenes; additive loading; get current scene info.
• ●Play mode — enter and exit play mode; inspect runtime state; query loaded scenes.
• ●Asset queries — list, read, and search scenes, prefabs, scriptable objects, build settings.
• ●Editor actions — execute menu items, trigger builds, run edit-mode and play-mode tests, clear the console.
• ●Project introspection — assembly definitions, package manifest, project settings.

Roughly 70 tools total. See Unity Integration for end-to-end setup.

Configuration

mcp:
  servers:
    unity:
      command: ["node", "/path/to/mcp-unity-plus/Server~/build/index.js"]

Tools from the server appear in the assistant's toolbox prefixed mcp__unity__ (e.g. mcp__unity__load_scene). Read-only tools auto-execute; destructive tools always prompt.

Security

MCP servers run as separate processes on your machine. Dynamo doesn't sandbox them — trust is the same as installing any CLI tool. Review the server source before registering it.

Dynamo prompts for confirmation the first time a new MCP server is registered and before it runs any destructive tool from one.