Godot MCP

To use Godot MCP with Cline, add the following configuration to your Cline MCP settings file located at ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json.

{
  "mcpServers": {
    "godot": {
      "command": "npx",
      "args": ["@coding-solo/godot-mcp"],
      "env": {
        "DEBUG": "true"
      },
      "disabled": false,
      "autoApprove": [
        "launch_editor",
        "run_project",
        "get_debug_output",
        "stop_project",
        "get_godot_version",
        "list_projects",
        "get_project_info",
        "create_scene",
        "add_node",
        "load_sprite",
        "export_mesh_library",
        "save_scene",
        "get_uid",
        "update_project_uids"
      ]
    }
  }
}

To add Godot MCP to Claude Code, use the claude mcp add command. You can optionally provide the path to your Godot executable and enable debug logging using environment variables.

Basic installation:

claude mcp add godot -- npx @coding-solo/godot-mcp

Installation with environment variables:

claude mcp add godot -e GODOT_PATH=/path/to/godot -e DEBUG=true -- npx @coding-solo/godot-mcp

To build the project from source, clone the repository, install dependencies, and run the build script. After building, point your MCP client to build/index.js instead of using npx.

git clone https://github.com/Coding-Solo/godot-mcp.git
cd godot-mcp
npm install
npm run build

For any other MCP-compatible client, use the following JSON configuration. You can specify GODOT_PATH to override automatic detection and DEBUG to enable detailed server-side logging.

{
  "mcpServers": {
    "godot": {
      "command": "npx",
      "args": ["@coding-solo/godot-mcp"],
      "env": {
        "GODOT_PATH": "/path/to/godot",
        "DEBUG": "true"
      }
    }
  }
}

You can configure Godot MCP in Cursor using the UI or a project-specific configuration file.

Using the Cursor UI

1. Go to Cursor Settings > Features > MCP.
2. Click + Add New MCP Server.
3. Set Name to godot.
4. Set Type to command.
5. Set Command to npx @coding-solo/godot-mcp.
6. Click Add.

Using Project-Specific Configuration

Create a .cursor/mcp.json file in your project directory:

{
  "mcpServers": {
    "godot": {
      "command": "npx",
      "args": ["@coding-solo/godot-mcp"],
      "env": {
        "DEBUG": "true"
      }
    }
  }
}

The following environment variables can be used to configure the Godot MCP server:

Common troubleshooting steps:

• Godot Not Found: Set the GODOT_PATH environment variable to your Godot executable path.
• Connection Issues: Ensure the server is running and restart your AI assistant.
• Invalid Project Path: Ensure the path points to a directory containing a project.godot file.
• Build Issues: Ensure all dependencies are installed by running npm install.

Cursor-Specific Troubleshooting:

• Ensure the MCP server is enabled in Settings > MCP.
• MCP tools require the Agent chat profile (Cursor Pro or Business subscription).
• Use "Yolo Mode" to automatically run MCP tool requests.

Initialize the GodotServer class with an optional GodotServerConfig object to customize the MCP server behavior.

Configuration Options:

• godotPath (string): Path to the Godot executable. If not provided, the server attempts auto-detection.
• debugMode (boolean): Enables debug logging to stderr.
• godotDebugMode (boolean): Enables --debug-godot flag when executing Godot operations.
• strictPathValidation (boolean): If true, the server will throw an error if it cannot find a valid Godot executable. If false, it falls back to common default paths (which may fail).

The Godot MCP server requires a valid path to the Godot executable. If the server cannot automatically detect it, you must set the GODOT_PATH environment variable.

If strictPathValidation is enabled in the server configuration, the server will exit if the provided path is invalid.

Adds a new node to an existing Godot scene.

Arguments:

• projectPath (required): Path to the project.
• scenePath (required): Path to the target scene file.
• nodeType (required): Built-in Godot class name (e.g., Sprite2D).
• nodeName (required): The name of the new node.
• parentNodePath (optional): Path to the parent node within the scene.
• properties (optional): An object containing properties to set on the new node.

Exports a .meshlib file from a Godot scene.

Arguments:

• projectPath (required): Path to the project.
• scenePath (required): Path to the scene containing 3D meshes.
• outputPath (required): Path where the library should be saved.
• meshItemNames (optional): An array of specific mesh item names to include.