Unity MCP 統合フレームワーク

What is Unity MCP 統合フレームワーク?

Unity MCP 統合フレームワーク connects the Unity Editor to AI language models like Claude or to CLI (curl) via HTTP, using the Model Context Protocol (MCP). It allows you to directly control Unity Editor—inspect scenes, execute C# code, capture screenshots, and manage Play Mode—from outside the editor.

How to use Unity MCP 統合フレームワーク?

Install the Unity package via Package Manager (Add package from git URL…). The HTTP server auto-starts on port 27182 (fallback 27182–27199). For Claude Desktop/Code, download the TypeScript MCP client using the built‑in installer and paste the generated config JSON. You can also call endpoints directly with curl. Configure options under Edit > Preferences > Unity MCP.

Key features of Unity MCP 統合フレームワーク

• HTTP + UDP auto‑discovery for multiple Unity Editors
• Works with MCP (Claude) and plain HTTP (curl, CI)
• Editor panel screenshot capture (Windows only)
• Built‑in C# code execution via Roslyn
• Extensible plugin architecture with auto‑registration
• Safe/Unsafe idempotency classification to prevent duplicate side effects

Use cases of Unity MCP 統合フレームワーク

• AI‑assisted game development (Claude reading hierarchy, adjusting objects)
• Automated CI/CD testing of Unity projects via curl scripts
• Remote inspection and screenshot of Editor windows
• Multi‑Editor project management with named routing
• Programmatic Play Mode control for regression tests

FAQ from Unity MCP 統合フレームワーク

What’s the difference between using MCP and direct HTTP?

MCP (stdio) is intended for AI model tools like Claude Desktop; direct HTTP allows scripts, CI, or any HTTP client (curl) to interact with Unity without the TypeScript server.

What are the runtime requirements?

Unity 2022.3 or later (up to Unity 6000), .NET/C# 9.0 (Editor side), and Node.js 18.0+ (TypeScript MCP server).

How does idempotency work?

Each command is marked Safe (read‑only, safe to retry) or Unsafe (mutating). The TypeScript client uses err.cause.code to retry only before a handshake for Unsafe commands, structurally preventing duplicate side effects.

Is this secure?

Yes. The HTTP server binds to 127.0.0.1 by default (loopback only). The /execute_code endpoint can be disabled in settings. External network exposure is not supported.

Can I create custom handlers?

Yes. Implement IMcpCommandHandler or IMcpResourceHandler in C# (auto‑detected by reflection) or extend BaseCommandHandler in TypeScript (place in src/handlers/). Prompts are also extensible via BasePromptHandler.