unity-mcp and better-godot-mcp
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 better-godot-mcp
n24q02m/better-godot-mcp
MCP server for Godot Engine - composite tools optimized for AI agents
Bundles 18 specialized tools for scene graph manipulation, GDScript authoring, shader editing, and animation/physics/audio configuration—all operable without a running Godot instance via direct `.tscn` file parsing. Implements token-optimized compressed tool descriptions with on-demand help retrieval, and integrates with Claude, Gemini, and standard MCP clients through npm/Docker distribution. Supports zero-config browser-based credential setup with encrypted local storage.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work