GladeKit Unity MCP — Connect AI Clients to Unity

Main

• Install the Unity bridge first (it auto-starts on localhost:8765), then connect an MCP client using uvx gladekit-mcp per README.

• Treat tool count and discovery as part of workflow: README claims 235+ tools and suggests get_relevant_tools for extended categories.

• If uvx isn’t found (common on Windows/Unity PATH), README suggests using pip install gladekit-mcp and running python -m gladekit_mcp instead.

Source-backed notes

• README shows Unity git package install URL with ?path=/unity-bridge and says the bridge runs on localhost:8765.
• README provides Claude Code one-liner: claude mcp add ... -- uvx gladekit-mcp and JSON snippets for other clients.
• README includes a troubleshooting note about PATH and a fallback to pip install gladekit-mcp + python -m gladekit_mcp.

FAQ

• What runs inside Unity vs outside?: README says Unity runs a bridge package; your AI client launches the MCP server via uvx/pip.
• Which clients are supported?: README lists Claude Code, Cursor, Windsurf, Claude Desktop, VS Code, and Unity AI Gateway config examples.
• What’s the common failure mode?: README calls out PATH differences (Unity vs terminal) and suggests adding PATH or switching to python -m mode.