A comprehensive integration between Godot Engine and AI assistants using the Model Context Protocol (MCP). This plugin allows AI assistants to interact with your Godot projects, providing powerful capabilities for code assistance, scene manipulation, and project management.

• Full Godot Project Access: AI assistants can access and modify scripts, scenes, nodes, and project resources
• Two-way Communication: Send project data to AI and apply suggested changes directly in the editor
• Command Categories:
  • Node Commands: Create, modify, and manage nodes in your scenes
  • Script Commands: Edit, analyze, and create GDScript files
  • Scene Commands: Manipulate scenes and their structure
  • Project Commands: Access project settings and resources
  • Editor Commands: Control various editor functionality

git clone https://github.com/ee0pdt/godot-mcp.git
cd godot-mcp

cd server
npm install
npm run build
# Return to project root
cd ..

1. Edit or create the Claude Desktop config file:

   # For macOS
   nano ~/Library/Application\ Support/Claude/claude_desktop_config.json

2. Add the following configuration (or use the included claude_desktop_config.json as a reference):

   {
     "mcpServers": {
       "godot-mcp": {
    	 "command": "node",
    	 "args": [
    	   "PATH_TO_YOUR_PROJECT/server/dist/index.js"
    	 ],
    	 "env": {
    	   "MCP_TRANSPORT": "stdio"
    	 }
       }
     }
   }

   Note: Replace PATH_TO_YOUR_PROJECT with the absolute path to where you have this repository stored.

3. Restart Claude Desktop

1. Open Godot Engine
2. Select "Import" and navigate to the cloned repository
3. Open the project.godot file
4. The MCP plugin is already enabled in this example project

After setup, you can work with your Godot project directly from Claude using natural language. Here are some examples:

@mcp godot-mcp read godot/editor/current_script

I need help optimizing my player movement code. Can you suggest improvements?

@mcp godot-mcp run get-scene-tree

Add a cube in the middle of the scene and then make a camera that is looking at the cube.

@mcp godot-mcp read godot/scene/current

Create an enemy AI that patrols between waypoints and attacks the player when in range.

• "Create a main menu with play, options, and quit buttons"
• "Add collision detection to the player character"
• "Implement a day/night cycle system"
• "Refactor this code to use signals instead of direct references"
• "Debug why my player character falls through the floor sometimes"

Static resources (no parameters):

• godot/editor/current_script - Currently edited script content and metadata.
• godot/scene/current - Current scene structure.
• godot/scene/edited - Currently edited scene snapshot (includes stable node ids).
• godot/scenes - List of all scenes in the project.
• godot/scripts - List of all scripts in the project.
• godot/project/structure - Directory and file counts.
• godot/project/settings - Key project settings and input map.
• godot/project/resources - Categorized resources.
• godot/editor/state - Editor state snapshot.
• godot/editor/selected_node - Currently selected node info.

Dynamic resources (templates):

• godot/script/{path} - Read any script by path.
  Example: @mcp godot-mcp read godot/script/res://scripts/player.gd
• godot/script/metadata/{path} - Read script metadata by path.
• godot/scene/{path} - Read raw .tscn/.scn text by path.
  Example: @mcp godot-mcp read godot/scene/res://scenes/main.tscn
• godot/scene/{path}/structure - Read scene structure by path.
• godot/scene/edited/{properties_csv} - Edited scene snapshot including selected properties.
  Example: @mcp godot-mcp read godot/scene/edited/position,rotation
• godot/resource/{path} - Read text-based Godot resources (e.g., .tres) by path.

• create_node - Create a new node
• delete_node - Delete a node
• update_node_property - Update a node property
• get_node_properties - Get all properties of a node
• list_nodes - List child nodes under a parent

• create_script - Create a new GDScript file
• edit_script - Edit an existing script
• get_script - Read a script’s content
• create_script_template - Generate boilerplate locally
• get_script_metadata - Read script metadata (used by resources)

• create_scene - Create a new empty scene
• save_scene - Save the current scene
• open_scene - Open a scene in the editor
• get_current_scene - Get current scene info
• get_scene_structure - Get structure for a scene by path
• get_scene_text - Read raw scene text by path

• get_project_info - Get project metadata
• get_project_structure - Get project structure
• get_project_settings - Get key project settings
• list_project_files - List project files by extension
• list_project_resources - List categorized resources
• get_file_text - Read a text-based file by path

• execute_editor_script - Execute arbitrary GDScript in the editor context

• Ensure the plugin is enabled in Godot's Project Settings
• Check the Godot console for any error messages
• Verify the server is running when Claude Desktop launches it

• Reload Godot project after any configuration changes
• Check for error messages in the Godot console
• Make sure all paths in your Claude Desktop config are absolute and correct

If you want to use the MCP plugin in your own Godot project:

1. Copy the addons/godot_mcp folder to your Godot project's addons directory
2. Open your project in Godot
3. Go to Project > Project Settings > Plugins
4. Enable the "Godot MCP" plugin

Contributions are welcome! Please feel free to submit a Pull Request.

For more detailed information, check the documentation in the docs folder:

• Getting Started
• Installation Guide
• Command Reference
• Architecture

This project is licensed under the MIT License - see the LICENSE file for details.