Unit API Communicator Mcp Server

Created By
SamDreamsMaker3 months ago
Control Unity Editor from AI agents. 200+ MCP tools for GameObjects, Scenes, Assets, Materials, Prefabs, Terrain, Physics, Lighting, and more. Works with Claude, Cursor, Windsurf, VS Code Copilot — any MCP client. Zero config: just npx and go.
Overview

Control Unity Editor from Any AI Agent

uac-mcp-server bridges AI agents to Unity Editor via the Model Context Protocol. Create GameObjects, build scenes, manage assets, configure materials — all from natural language.

200+ Tools

  • GameObjects — Create, delete, transform, clone, tag, layer, add/remove components
  • Scenes — Open, save, create, close, list loaded scenes
  • Assets — Create, delete, rename, move, search
  • Materials — Set colors, textures, shaders, floats
  • Prefabs — Create, instantiate, apply overrides, unpack
  • Build — Switch platform, configure player settings, start builds
  • Terrain — Heightmaps, paint, trees, grass, layers
  • Physics — Rigidbodies, colliders, raycasts, joints
  • Lighting — Create lights, reflection probes, bake lightmaps
  • Animation — Animators, controllers, states, clips
  • UI — Canvas, buttons, text, layout elements
  • Camera — Create, configure, take screenshots
  • Console — Read logs, errors, clear output
  • And more: Navigation, Particles, Audio, Timeline, Addressables...

Quick Setup

npx -y uac-mcp-server

Works with Claude Desktop, Claude Code, Cursor, Windsurf, VS Code Copilot, and any MCP-compatible client.

How It Works

The server auto-discovers all endpoints from the Unity API Communicator plugin running in your Unity Editor. 54 core tools have fully typed Zod schemas for precise parameter handling. All other endpoints are registered with generic schemas — the AI figures out the parameters from tool descriptions.

Prerequisites

  1. Unity API Communicator plugin installed in Unity Editor
  2. Node.js 18+

Server Config

{
  "mcpServers": {
    "unity": {
      "command": "npx",
      "args": [
        "-y",
        "uac-mcp-server"
      ]
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
SamDreamsMaker
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago