Glade MCP server

Glade MCP

Connect Cursor, Claude Code, Windsurf, Claude Desktop, and other AI clients directly to your Unity or Godot editor.

Unity (2021.3+): 275 tools across 20 categories, full Unity-aware system prompt, GLADE.md project context, script semantic search, skill calibration, free CC0 asset pipeline, cloud intelligence layer with RAG and cross-session memory.

Godot (4.3+): 115 native tools across 17 categories - scene/node, scripts, resources, signals, physics and edit-time spatial queries, 2D (sprites, tilemaps, parallax), audio, particles, animation and AnimationTree, camera, navigation, UI, lighting and WorldEnvironment, runtime, export, and project introspection.

Both engines: one-call vetted gameplay scaffolders (controllers, enemies, combat, menus, save system), a verification loop (lookatgameview screenshots, runtime-event observation, playability probes), surgical script editing with true findreferences / rename_symbol, and build/export tools so the agent can ship what it built.

The MCP server auto-detects which editor is running (Unity on :8765, Godot on :8766) and exposes the matching tool set.

Quick Start

1. Install the editor bridge

Glade MCP supports both Unity and Godot. Both bridges live in this repo: unity-bridge/ is a UPM package, godot-bridge/ wraps the editor addon at godot-bridge/addons/com.gladekit.mcp-bridge/. Install the one for your engine.

Unity (2021.3+)

In Unity, open Window > Package Manager > + > Add package from git URL...

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

The Unity bridge starts automatically on localhost:8765. Window > GladeKit MCP shows bridge / client status and has one-click Copy MCP Config and Copy Unity AI Gateway Config buttons.

Godot (4.3+)

1. Download com.gladekit.mcp-bridge.zip from the latest Godot bridge release. (Grab the zip asset under Assets - not "Source code".) From source instead: copy godot-bridge/addons/com.gladekit.mcp-bridge/ out of this repo.
2. Move the com.gladekit.mcp-bridge/ folder into your project's addons/ directory, so the final path is /addons/com.gladekit.mcp-bridge/plugin.cfg.
3. In Godot: Project → Project Settings → Plugins → enable GladeKit MCP Bridge.

The Godot bridge starts automatically on localhost:8766. You should see a confirmation line in the editor Output panel:

[GladeKit MCP Bridge] listening on ws://127.0.0.1:8766  (v0.7.13, 115 tools registered, thread-polled at 200Hz)

The bridge writes a per-session auth token to ~/.gladekit/godot-bridge-8766.token; the MCP server picks it up automatically, so a web page can't drive your editor through the local socket.

Supported: Godot 4.3+ GDScript projects, Forward+ and Compatibility renderers, 2D and 3D. Not yet supported: Godot Mono / C# projects. The bridge is editor-only; it never runs in exported games.

Engine auto-detection: the MCP server probes both ports on startup and exposes the matching tool set. Running both editors at once? Set GLADEKITMCPFORCE_ENGINE=unity or =godot to pin a specific engine.

2. Connect your AI client

Install uv (one-time):

• Mac/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh
• Windows: powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Then add the MCP config to your AI client. The client launches the MCP server automatically - no manual server step.

Shortened. The full README is on GitHub.