The shortlist
Editor bridges let an agent act inside the engine rather than only editing script files: building scenes, running the project and reading its errors. The right one is simply the one for the engine you use.
Documentation-based starting points, not hands-on benchmarks. Check each option's fit, setup and costs below. Compare them with the same worksheet.
16k stars · Costs not checked · C#
A Unity editor bridge for agent-driven project work. Check the current tool list, Unity version support and installation instructions before connecting it to a copy of your project.
— Your setup can't run Python 3.10 or later with uv alongside Unity; the bridge depends on it.
6.5k stars · Costs not checked · JavaScript
Launches the Godot editor, runs projects in debug mode and captures their output, giving an agent the feedback loop it needs to fix its own game code, plus scene editing tools.
33k stars · Costs not checked · Python
For modelling rather than game logic: prompt-driven 3D modelling and scene editing in Blender through an addon and an MCP server run with uv.
— You can't install the Blender addon; the server controls Blender through it.
These bridges act on your open project, so commit or back up first: an agent can delete scenes and assets as easily as it creates them. Each needs its editor-side plugin or addon installed and the editor running, and none of them is made by the engine vendor.
Check the linked product sources, supported languages, regional availability, permissions and current costs for your actual setup.
Google Analytics helps us understand visits. It stays off unless you allow it. Your choice is remembered for up to 180 days. Privacy policy
