Unity AI Bridge
Related Servers
Alternatives to Unity AI Bridge
- AlicenseNot gradedqualityAmaintenanceSeamless automation and intelligent control over your Unity projects. By integrating with the MCP server and client, it allows AI agents or external tools to interact with your Unity environment—creating, modifying, and managing GameObjects, Components, Assets, Scenes, and more.4,331Apache 2.0
Related Servers
- AlicenseBqualityDmaintenanceControl 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.626 npmMIT
- AlicenseAqualityAmaintenanceMCP server for controlling the Unity Editor from AI clients. 140+ tools for scenes, GameObjects, components, assets, Shader Graph, PlayTest DSL, screenshots with visual diff, batch operations with Undo rollback, and in-editor chat. Token-efficient plain-text protocol.3628MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query and control the Unity Editor, supporting scene management, GameObject manipulation, asset browsing, play mode control, and real-time editor operations through 52+ tools.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents (like Claude Code, Cursor) to directly operate Unity scenes via MCP protocol, with tools for scene hierarchy, object creation/deletion, and transform modification.5 npm1ISC

glade-mcpofficial
AlicenseNot gradedqualityAmaintenanceConnect any MCP-compatible AI client (Claude Code, Cursor, Windsurf) to Unity or Godot. 300+ granular tools, an editor aware system prompt, game design document project context, script semantic search, and skill calibration.222MIT- AlicenseNot gradedqualityFmaintenanceEnables AI agents to interact with Unity projects through multimodal vision, code analysis, asset management, and scene manipulation. Supports real-time Unity editor control, project search, script creation, and visual debugging through screenshots.32MIT
TDQS
Scored across 65 tools
Tools are clearly separated by domain (assets, gameobjects, prefabs, light probes, profiler, reflection, scripting, scenes, etc.). Even overlapping areas like runtime-invoke vs reflection-method-call are distinguished by usage context. Each tool has a distinct purpose.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., assets-copy, gameobject-find, scene-open). Exceptions like lightprobe-analyze still follow the pattern. This makes the set predictable and easy to navigate.
With 65 tools, the count is high but appropriate for the breadth of Unity editor automation covered. The scope justifies the number, though some tools could potentially be merged (e.g., object-get-data and object-modify). Still, it remains well-scoped for a comprehensive bridge.
The tool set covers all major Unity editor workflows: assets, gameobjects, prefabs, scenes, scripts, packages, reflection, profiler, light probes, tests, and screenshots. It includes CRUD operations, analysis, and debugging utilities, with no obvious missing functionality.