godot-mcp and Gopeak-godot-mcp
These two tools are competitors, both providing MCP server implementations for Godot Engine control, with GoPeak offering a broader feature set including scene management, LSP, and debugging capabilities.
About godot-mcp
tugcantopaloglu/godot-mcp
MCP server for full Godot 4.x engine control — 149 tools for AI-driven game development
Implements a TCP-based runtime interaction server alongside a TypeScript MCP server, enabling both headless scene parsing (via GDScript operations) and live game manipulation through arbitrary code execution, property inspection, and signal management. Covers 149 tools spanning physics, networking, audio, animation trees, UI theming, shader parameters, skeletal animation, procedural geometry, and export automation—essentially exposing Godot's entire API surface to AI assistants. Designed for AI-driven game development workflows where LLMs can prototype, test, debug, and iterate games through a single MCP interface.
About Gopeak-godot-mcp
HaD0Yun/Gopeak-godot-mcp
GoPeak — The most comprehensive MCP server for Godot Engine. 95+ tools: scene management, GDScript LSP, DAP debugger, screenshot capture, input injection, ClassDB introspection, CC0 asset library. npx gopeak
Implements MCP protocol over stdio with automatic reconnection and cursor-based pagination to manage token efficiency across 110+ tools. Built in TypeScript/Node.js, it communicates with Godot via GDScript bridge addons for live scene/resource editing and runtime inspection without restarting the editor. Dynamic tool groups automatically activate based on AI intent, exposing only relevant capabilities while keeping the token footprint minimal.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work