Godot Pro MCP Server
Godot editor API access via 175 tools for AI-powered game development workflows.
Data last scanned today · Reviewed today
Overview
Godot Pro MCP Server provides a bridge between AI assistants and the Godot game engine through a WebSocket-based architecture. By integrating with Godot's editor API, the plugin enables AI agents to interact directly with the scene tree, UndoRedo system, and editor runtime environment. Users can choose from four distinct tool configurations ranging from 35 to 175 tools to match their specific AI client constraints. While the open repository provides the necessary Godot addon, the core Node.js server component is distributed via a paid model to facilitate full editor connectivity.
Our verdict
This server carries a high risk level with a security score of 43/100. It lacks read-only mode, meaning every installation grants full write access to your project environment, and the project is community-maintained rather than being supported by the official Godot vendor. We recommend this tool only for developers who are comfortable with the risks of third-party editor plugins and have robust version control to revert accidental changes.
- Supports specialized tool modes to fit various AI client limits
- Zero direct dependencies minimize supply-chain surface area
- Features 175 distinct tools for deep editor integration
- Active development with a commit twelve days ago
- Every installation defaults to full write access without read-only restrictions
- License is marked as NOASSERTION
- Requires a paid purchase to access the required Node.js server
- Lack of official vendor maintenance increases dependency risk
Tools
| Tool | Description | Risk |
|---|---|---|
| get_project_info | Project metadata, version, viewport, autoloads | low |
| get_filesystem_tree | Recursive file tree with filtering | low |
| search_files | Fuzzy/glob file search | low |
| get_project_settings | Read project.godot settings | low |
| set_project_setting | Set project settings via editor API | medium |
| uid_to_project_path | UID → res:// conversion | low |
| project_path_to_uid | res:// → UID conversion | low |
| get_scene_tree | Live scene tree with hierarchy | low |
| get_scene_file_content | Raw .tscn file content | low |
| create_scene | Create new scene files | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›Is the Godot MCP Pro server available in the public GitHub repository?
No, the public repository only contains the Godot addon. The MCP server component is distributed as part of a paid package available via Buy Me a Coffee or itch.io.
›How do I communicate between the MCP server and the Godot editor?
The server connects to the Godot editor plugin via a WebSocket connection on port 6505 by default.
›Can I adjust the number of tools exposed to my AI client?
Yes, you can specify different modes such as --3d, --lite, or --minimal in your server configuration arguments to reduce the tool count if your client has limitations.
›What should I do if my AI client does not support MCP?
You can use the provided CLI mode, which allows you to execute commands directly from a terminal. The CLI requires the Godot editor to be running with the plugin enabled and uses ports in the 6510-6514 range.
›What are the setup requirements for the server component?
You must install the Node.js environment, run npm install in the server directory, and execute the build command to generate the necessary JavaScript files before running the server.
Badge
Maintain this server? Add the live badge to your README.