Godot MCP Server

Godot mcp mcp server lets Claude, Cursor and other MCP clients work with Godot MCP directly. MCP server for interacting with the Godot game engine, providing tools for editing, running, debugging, and managing scenes in Godot projects.

What Godot MCP does

/$$ /$$ /$$$$$$ /$$$$$$$ | $$$ /$$$ /$$__ $$| $$__ $$ | $$$$ /$$$$| $$ _/| $$ \ $$ | $$ $$/$$ $$| $$ | $$$$$$$/ | $$ $$$| $$| $$ | $$/ | $$\ $ | $$| $$ $$| $$ | $$ / | $$| $$$$$$/| $$ |/ |/ _/ |/ ```

Godot MCP enables AI agents to launch the Godot editor, run projects, capture debug output, and control project execution. This direct feedback loop helps agents understand what works and what doesn't in real Godot projects, leading to better code generation and debugging assistance.

Key capabilities

• Launch Godot Editor — Open the Godot editor for a specific project
• Run Godot Projects — Execute Godot projects in debug mode
• Capture Debug Output — Retrieve console output and error messages
• Control Execution — Start and stop Godot projects programmatically
• Get Godot Version — Retrieve the installed Godot version
• List Godot Projects — Find Godot projects in a specified directory
• Project Analysis — Get detailed information about project structure
• Scene Management —

Tools it exposes

Once connected, the assistant can call these 6 tools directly:

• Name — godot
• Type — command
• Command — npx @coding-solo/godot-mcp
• Variable — Description
• GODOT_PATH — Path to the Godot executable (overrides automatic detection)
• DEBUG — Set to "true" to enable detailed server-side debug logging

Installing the godot mcp mcp server

The server is distributed via npm as @coding-solo/godot-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

The server reads 2 environment variables: DEBUG, GODOT_PATH. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Godot Engine installed on your system - Node.js (>=18.0.0) and npm - An AI agent that supports MCP

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Godot MCP sits in that group, and the shape of its toolset — Name, Type, Command among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the godot mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.