Design Narrow MCP Read and Write Tools
Give each MCP tool one bounded job, an explicit input contract, and a result small enough to review before widening permissions.
Learning paths
Design narrow MCP tools, reduce context cost, gate changes with evidence, apply high-value Unity workflows, and protect permission boundaries.
Ordered roadmap
Read each step in order. The connector note explains why the next topic follows.
Give each MCP tool one bounded job, an explicit input contract, and a result small enough to review before widening permissions.
Use filtering, pagination, summaries, and progressive discovery so only decision-relevant Unity context reaches the model.
Turn an agent request into an inspect, plan, approve, change, test, and review sequence with evidence at every boundary.
Apply narrow MCP capabilities to console triage, scene inspection, prefab review, build checks, and tests without granting broad control.
Keep least privilege, secret custody, untrusted tool output, and human approval explicit before an MCP workflow can mutate a project.