unity-mcp and agent-bridge-for-unity
These are **competitors**: both provide MCP servers that expose Unity Editor functionality to AI assistants, with overlapping core capabilities (asset management, scene building, editor control) but different implementation scopes—Unity MCP with broader adoption and agent-bridge-for-unity with a larger tool count (243 vs. unspecified).
About unity-mcp
CoplayDev/unity-mcp
Unity MCP acts as a bridge, allowing AI assistants (like Claude, Cursor) to interact directly with your Unity Editor via a local MCP (Model Context Protocol) Client. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.
Implements a comprehensive Python-based MCP server using HTTP transport that operates locally within the Unity Editor, exposing 40+ tools across physics, animation, graphics, builds, and scene management alongside introspection resources like `unity_reflect` for live API inspection. The architecture supports multi-instance routing, async long-running operations with polling, batch execution for performance optimization, and integrates with popular LLM clients (Claude, Cursor, VS Code Copilot, Windsurf) through configurable connection protocols. Available as a Git-based package in the Unity Package Manager, Asset Store, and OpenUPM with Python 3.10+ and the `uv` package manager as runtime dependencies.
About agent-bridge-for-unity
sebastiankurvers-dev/agent-bridge-for-unity
Let AI operate the Unity Editor — 243 MCP tools for scene building, visual QA, Play Mode, and more.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work