GladeKit MCP

Connect Cursor, Claude Code, Windsurf, Claude Desktop, and VS Code to your Unity Editor.

222+ tools. A full Unity-aware system prompt. GLADE.md project context. Script semantic search. Skill calibration. All free, all local - no GladeKit account required.

Quick Start

1. Install the Unity bridge

In Unity: Window > Package Management > Package Manager > + > Install package from git URL...

https://github.com/Glade-tool/glade-mcp-unity.git?path=/unity-bridge

The bridge starts automatically when Unity opens. It runs on localhost:8765.

2. Install the MCP server

# Recommended — no install step, always latest:
uvx gladekit-mcp

# Or install permanently:
pip install gladekit-mcp

3. Add to your AI client

Pick your client below and add the config. Then open your Unity project and start prompting.

Claude Code (auto-connect)

Open your project root in Claude Code - if you cloned this repo, the .mcp.json auto-connects. Otherwise add to your Claude Code MCP settings:

{
  "mcpServers": {
    "gladekit-unity": {
      "command": "uvx",
      "args": ["gladekit-mcp"]
    }
  }
}

Cursor

Cursor Settings > MCP > Add new MCP server:

{
  "mcpServers": {
    "gladekit-unity": {
      "command": "uvx",
      "args": ["gladekit-mcp"]
    }
  }
}

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "gladekit-unity": {
      "command": "uvx",
      "args": ["gladekit-mcp"]
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "gladekit-unity": {
      "command": "uvx",
      "args": ["gladekit-mcp"]
    }
  }
}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in your workspace:

{
  "servers": {
    "gladekit-unity": {
      "type": "stdio",
      "command": "uvx",
      "args": ["gladekit-mcp"]
    }
  }
}

Why GladeKit MCP?

| Feature | GladeKit MCP | unity-mcp (CoplayDev) | | ----------------- | ---------------------------------------------------------------------------------------------------- | ---------------------- | | Tools | 222 granular tools | ~40 consolidated tools | | System prompt | Full Unity intelligence — render pipeline detection, input system routing, tool discipline rules | None | | Project context | GLADE.md — inject your game design doc into every request | None | | Script search | Semantic search via OpenAI embeddings (bring your own key) | None | | Skill calibration | Auto-detects beginner/expert, adapts response verbosity | None | | In-session memory | remember_for_session — AI stores and recalls facts mid-conversation | None | | Paid tier | GLADEKIT_API_KEY — RAG knowledge base + cross-session memory | None | | License | MIT | MIT |

All features in the table above are free and local — no GladeKit account needed.

Features

222 tools across 14 categories

Scene • GameObjects • Scripts • Prefabs • Materials • Lighting • VFX & Audio • Animation • IK • Physics • Camera • UI • Input System • Terrain & NavMesh

All 222 tools are dispatchable. Claude Code sees 82 curated tools by default (Claude Code has a practical 128-tool limit). Use get_relevant_tools to discover extended tools for specialized work (blend trees, NavMesh, IK, Cinemachine, etc.).

GLADE.md — project game design doc

Create a GLADE.md file in your Unity project root. The MCP server reads it and injects it into every request. Works as a permanent context layer: your game's design intent, conventions, and constraints are always in scope.

# My Game

Genre: 2D platformer  
Player: CharacterController, double jump enabled  
Art style: pixel art, 16x16 sprites  
Naming: PascalCase for scripts, snake_case for folders

Script semantic search

With OPENAI_API_KEY set, the server finds relevant scripts using cosine similarity rather than filename matching. Ask "how does the enemy spawn?" and the right script surfaces — even if it's not named EnemySpawner.

Skill calibration

The server tracks vocabulary across your messages and detects whether you're a Unity beginner or expert. Beginners get plain-language explanations and encouraging framing. Experts get terse, technical responses. Calibration persists to .gladekit/skill_level.json in your project.

Paid tier — GLADEKIT_API_KEY

Coming soon.

Environment Variables

| Variable | Required | Description | | ------------------ | -------- | --------------------------------------------------- | | UNITY_BRIDGE_URL | No | Unity bridge URL (default: http://localhost:8765) | | OPENAI_API_KEY | No | Enables script semantic search | | GLADEKIT_API_KEY | No | Enables RAG knowledge base + cross-session memory |

Troubleshooting

Bridge not connecting

• Open Unity and wait for it to finish importing assets — the bridge starts automatically
• Check Window > GladeKit MCP in Unity for bridge status
• Verify nothing else is using port 8765: lsof -i :8765 (Mac/Linux) or netstat -ano | findstr 8765 (Windows)

uvx not found

• Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh (Mac/Linux) or pip install uv
• Or use pip install gladekit-mcp and replace uvx gladekit-mcp with python -m gladekit_mcp

Tools not appearing in Claude Code

• Claude Code has a practical ~128-tool limit. GladeKit shows 82 curated tools by default — this is intentional. All 222 are dispatchable: use the get_relevant_tools tool to find extended tools by task description.

GLADE.md not being picked up

• The file must be named exactly GLADE.md (case-sensitive on Mac/Linux) and placed in the Unity project root (same directory as Assets/, Packages/, ProjectSettings/)

Architecture

[AI Client: Cursor / Claude Code / Windsurf / Claude Desktop]
         │
         │ stdio MCP protocol
         ▼
[gladekit_mcp Python process]
    bridge.py → HTTP localhost:8765
    prompts.py → system prompt (auto-reads render pipeline, input system, GLADE.md)
    tools/ → 222 tool schemas + dispatch
    cloud.py → optional GLADEKIT_API_KEY → api.gladekit.dev
         │
         │ HTTP localhost:8765
         ▼
[Unity Bridge — C# Editor extension (UPM package)]
    UnityBridgeServer.cs → HttpListener on :8765
    222 ITool implementations
    UnityContextGatherer → scene, scripts, packages, render pipeline

Contributing

The Unity bridge (unity-bridge/) is the source of truth for C# tools. Adding a tool requires two files:

1. C# implementation (unity-bridge/Editor/Tools/Implementations/<Category>/MyTool.cs):

public class MyTool : ITool
{
    public string Name => "my_tool";
    public string Execute(Dictionary<string, object> args)
    {
        // ... Unity Editor API calls ...
        return ToolUtils.CreateSuccessResponse("Done", extras);
    }
}

2. Python schema (mcp-server/src/gladekit_mcp/tools/<category>.py):

Add an entry to the category's tool list following the existing format (OpenAI function-calling schema).

Tools are auto-discovered via reflection - no registration needed beyond these two files.

License

MIT: see LICENSE.

The GladeKit desktop app provides the full agentic loop experience (streaming, miss recovery, error tracking, memory UI) and is a separate commercial product.