Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
A MCP server for interacting with the Godot game engine, providing tools for editing, running, debugging, and managing scenes in Godot projects.
Drive the Unreal Engine 5.7 editor from any MCP client over a local TCP socket — 105 editor-automation tools (72 native C++ + 33 bridge-side). Native C++ plugin + thin Python bridge, 50ms round-trips. 498 tests, MIT.
Quality signal
57/100 (Good)
52/100 (Fair)
Install path
npx · high
uvx · low
Engagement
4 0 0 5,114
3 0 0 9
Tools
Launch Godot editor for projectsRun projects in debug mode with start/stop controlCapture console output and error messagesCreate and modify scenes and nodes including sprites and texturesExport 3D scenes as MeshLibrary resources for GridMapUID management for Godot 4.4+ to update resource references
Native C++ plugin with 151 editor automation toolsThin Python bridge for MCP client communication~50ms round-trip latency over local TCP socketSupports asset creation and inspection including Blueprints and Niagara FXCompatible with any MCP-compliant clientTested with Unreal Engine 5.7 (official) and 5.6 (prebuilt)
