← Back to blog

Unity MCP: Supported AI Clients (Cursor, Claude)

Which AI tools work with Unity MCP: one local unity-mcp server for Cursor, Claude Code, Codex, Windsurf, and Gemini CLI—shared Unity setup, smoke tests, and de…

Published · Updated
  • unity
  • unity-mcp
  • mcp
  • cursor
  • claude-code
  • codex
  • vberai

Which AI clients does Unity MCP support? Teams often assume each assistant needs its own Unity plugin. In practice Unity runs one local MCP Server (usually unity-mcp in the panel). Cursor, Claude Code, Codex, Windsurf, Cline, and Gemini CLI—any Model Context Protocol client—attach to the same bridge. What changes is client-side MCP config, not duplicate Unity packages.

Verify ports and labels against your VberAI Unity MCP build. Download: Unity MCP

Unity side: three steps for every client

  1. Package Manager → Add package from disk (Unity MCP install)
  2. Activate in Mcp Panel; Unity MCP Server shows Running (default port often 6589)
  3. Quick setup in the panel for your client, or paste endpoint / stdio into the client MCP list

If the server is not Running, every AI only sees disk .cs files, not Hierarchy / Console / selection.

Shared smoke test

  1. Read-only: list root GameObjects in the active scene
  2. Small write: create empty MCP_SmokeTest, then delete
  3. Commit before large agent edits; you still own Play mode and compile errors

Client comparison

AI clientTypical hook-upDeep dive
CursorPanel one-click → unity-mcp in Cursor MCP (Reload if needed)Cursor + Unity MCP workflow
Claude CodeQuick setup → Copy CLI commandClaude Code + Unity MCP
CodexAfter Running, add unity-mcp to Codex MCP settings (match panel)FAQ below; active instances
Windsurf / Cline / ContinueMCP entry + Reload, same as Cursor patternWorkflow guide
Gemini CLIQuick setup → Gemini CLI → copy commandCLI flow in Claude install guide

Best AI for Unity MCP? MCP is not tied to one LLM—use the client your repo already uses. Stable Running + visible tools beats switching models.

Shortest three steps per client (after Running)

Cursor

  1. Quick setup → Cursor → success toast
  2. Cursor Settings → MCP → unity-mcp + tools
  3. Read-only root node list

Claude Code

  1. Quick setup → Copy CLI command
  2. Run in Claude CLI environment
  3. Read-only root node list

Codex

  1. Copy panel URL or stdio
  2. Paste into Codex MCP config
  3. Restart Codex; empty tools → active instances

Scope

In scopeOut of scope
Hierarchy, components, attach scripts, Console (per tools)Builds, netcode, perf tuning
Swap clients on one serverOne Unity plugin per AI brand
Wire UI after Studio importFigma → Prefab without AI Studio

Godot decision FAQ: Do you need Godot MCP?

Next steps

  1. Not installed → Unity MCP install
  2. Running → Quick setup + smoke test for your client
  3. Video walkthrough → Unity MCP plugin guide

FAQ

Which AI works with Unity MCP?
Any MCP client that reaches local unity-mcp—commonly Cursor, Claude Code, Codex, Windsurf, Cline, Gemini CLI. See comparison table.

Two Unity plugins for Cursor and Claude?
No. One server in Unity; register MCP in each client.

Codex does not see Unity tools?
Check Running, matching config, client restart; then active instances.

Do I have to hand-write all C#?
For everyday gameplay scripts, usually not: AI can create and edit C# through Unity MCP, attach scripts to GameObjects, and tweak Inspector fields (within the plugin’s tools). You focus on diff review, compile errors, and Play-mode checks. Architecture, netcode, and hot paths still deserve explicit human judgment—not because MCP cannot write code, but because those areas need careful ownership.

More guides you might like