MCP Tooling

The Model Context Protocol is a shared wire format for giving AI assistants access to external tools. Dynamo uses it to drive your game engine: install the engine package and the editor's tools show up in chat, prefixed mcp__<engine>__<tool> (e.g. mcp__unity__load_scene).

Today the supported integration is Unity, shipped in the dynamo-unity package.

Driving the Unity Editor

The companion `dynamo-unity` package gives the assistant direct control of a running Unity Editor — and the connection stays live in Play Mode, so the model can drive and inspect your game while it runs. Roughly 70 tools (scenes, assets, play-mode input, runtime assertions, tests, builds, settings) become available in chat once the bridge is connected. See Unity Integration for the full setup.

A tool's permission level is derived from the annotations it declares: read-only tools auto-execute, destructive tools always prompt, and the rest prompt once per session.

Connecting & managing

• ●Startup — Dynamo reports the bridge state on launch: connected (with a tool count), reachable but the Unity Editor isn't responding, or not installed (with an install hint).
• ●`/mcp` — live bridge state, transport, tool/resource/prompt counts, and backend readiness; press r to reconnect.
• ●`/connect` — reconnect the engine bridge (handy after you start or restart the Unity Editor).

The model can manage the connection too, via admin tools: mcp_list_servers, mcp_server_reconnect, mcp_tool_enable / mcp_tool_disable (session-scoped), and mcp_resource_read / mcp_prompt_get for fetching the bridge's resources and prompts.