Get the FREE Ultimate OpenClaw Setup Guide →

godot

MCP server for interfacing with Godot game engine. Provides tools for launching the editor, running projects, and capturing debug output.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio coding-solo-godot-mcp node /absolute/path/to/godot-mcp/build/index.js \
  --env DEBUG="true" \
  --env GODOT_PATH="<path-to-godot-executable>"

How to use

The Godot MCP server exposes a suite of MCP endpoints to manage and interact with Godot projects from an AI assistant. You can launch the Godot editor for a specific project, run projects in debug mode, retrieve console output, and control project execution remotely. Built-in capabilities also include listing available projects, obtaining Godot version information, and performing project analysis. The server supports scene management tasks such as creating scenes, adding nodes with custom properties, loading assets into sprites, exporting 3D resources like MeshLibrary, and saving scenes with variant options. UID management is available for Godot 4.4+ to fetch or update UID references across resources. Configure the server in your MCP client (Cline or Cursor) and then issue high-level prompts like “Launch the Godot editor for /path/to/project,” “Run the project and show errors,” or “List all Godot projects in /projects.”

How to install

Prerequisites:

  • Godot Engine installed on the host
  • Node.js and npm installed
  • Access to a compatible AI assistant that supports MCP (e.g., Cline or Cursor)

Step 1 — Clone the repository

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

Step 2 — Install dependencies and build

npm install
npm run build

Step 3 — Run (local development)

node build/index.js

Step 4 — Configure your MCP client

  • For Cline, add a server entry pointing to the built index.js with DEBUG enabled (example in README).
  • For Cursor, configure a command-based MCP server with: node /absolute/path/to/godot-mcp/build/index.js.

Step 5 — Environment variables (optional)

  • GODOT_PATH: Path to the Godot executable (override automatic detection)
  • DEBUG: Set to "true" to enable detailed server-side logging

Step 6 — Verify installation

  • Ensure the MCP server is reachable from your AI assistant and that prompts such as launching the editor or listing projects return expected results.

Additional notes

Notes and tips:

  • The server configuration expects an absolute path to the built MCP index.js when used from external MCP clients.
  • If Godot is not found automatically, set GODOT_PATH to the Godot executable path via the environment to ensure proper detection.
  • Use DEBUG=true to troubleshoot integration with your AI assistant. Be mindful of verbose logs in production.
  • Ensure the MCP server process has permission to access your Godot projects directory.
  • When upgrading Godot or the MCP server, re-build to ensure compatibility with the latest APIs.

Related MCP Servers

Sponsor this space

Reach thousands of developers