All resources
Resources / MCP connection

Connect Claude to Godot.
Godot MCP setup.

To connect Claude Code, Cursor or Cline to Godot, add the community godot-mcp server by Coding-Solo (npx -y @coding-solo/godot-mcp) to your client, then ask for one real result, such as your Godot version. Your assistant can then inspect a project, run it, and read what happened.

Set up my client Community server
The connection you’re building
Your AI clientRequests an action
Godot MCP serverExposes a set of tools
stdio
Your Godot projectReturns output to the assistant

Diagram only · setup happens in your client

01

Connect Claude Code, Cursor or Cline.

This guide uses Coding-Solo’s godot-mcp, a community server that runs outside the editor. To weigh it against editor plugins such as Godot MCP Toolkit or Godot MCP Pro, see Godot MCP servers compared.

Before you startGodot installedNode.js 18+ and npmA folder with project.godotAn MCP-capable client
Claude Code

A small setup, step by step.

  1. Open a terminal in your Godot project folder.
  2. Run the command below to register the server.
  3. Restart Claude Code, then open /mcp to inspect the godot connection.
Claude Code documentation
Terminal · from your project folder

Register the local server with Claude Code. Run this in a terminal where claude, node, and npx are available.

claude mcp add --transport stdio godot -- npx -y @coding-solo/godot-mcp

The -y flag accepts npm’s install prompt. It does not approve MCP tool calls.

In Claude Code, use /mcp to check that the godot server connected. If it failed, inspect the error before trying a tool.

Try the first tool
Cursor

A small setup, step by step.

  1. Open your Godot project folder in Cursor.
  2. Create or edit .cursor/mcp.json with the configuration below.
  3. Open Cursor’s MCP settings, enable the server, and check its available tools. Use Agent to call them.
Cursor documentation
.cursor/mcp.json

Add the server to your project’s MCP configuration. If the file already has servers, merge the godot entry into mcpServers.

{
  "mcpServers": {
    "godot": {
      "command": "npx",
      "args": [
        "-y",
        "@coding-solo/godot-mcp"
      ],
      "type": "stdio"
    }
  }
}

The -y flag accepts npm’s install prompt. It does not approve MCP tool calls.

Check the godot server in Cursor’s MCP settings. Its tool list should include get_godot_version. Reload the connection if the new entry has not appeared.

Try the first tool
Cline

A small setup, step by step.

  1. In Cline, open MCP Servers → Configure → Configure MCP Servers.
  2. Add the godot entry under mcpServers in the JSON file it opens.
  3. Save, check the server’s tool list, and approve the first tool call when prompted.
Cline documentation
Cline extension · MCP settings JSON

Open the extension’s configuration from its MCP Servers panel. Keep other server entries when adding godot.

{
  "mcpServers": {
    "godot": {
      "command": "npx",
      "args": [
        "-y",
        "@coding-solo/godot-mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

The -y flag accepts npm’s install prompt. It does not approve MCP tool calls.

The godot entry should be enabled and list its tools. This example keeps autoApprove empty so you can review tool calls.

Try the first tool
Other clients

A small setup, step by step.

  1. Choose a local / stdio server in your client’s MCP settings.
  2. Use command npx with two arguments: -y and @coding-solo/godot-mcp.
  3. If your client uses mcpServers JSON, merge this entry. Otherwise enter those fields in its setup form.
Server setup reference
Local MCP server · stdio

Your client must support local stdio servers. The JSON below is a common format; use your client’s own configuration schema if it differs.

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

The -y flag accepts npm’s install prompt. It does not approve MCP tool calls.

Use your client’s server status and tool list to verify the connection. An HTTP URL field alone cannot launch this stdio server.

Try the first tool
02

Check the connection with a real result.

Copy a prompt into your AI client, then inspect the tool response there.

Read the engine version

Use the Godot MCP get_godot_version tool and show me the version it returns. If the tool is unavailable or fails, report the error instead of guessing.
What to look for

A completed tool call with the version of your installed Godot executable. A chat reply without a tool result does not verify the connection.

Starts with a version query.

Find the right project

Ask me for the absolute path to my Godot project folder. Then use get_project_info on that folder and report the project name and structure. Do not edit files or run the project yet.
What to look for

Project information for the folder you supplied, which contains project.godot. Check that it is the project you meant to connect.

Uses your actual project path.

Run, inspect, then stop

Ask me to confirm the absolute path of the Godot project to run. Use run_project, then get_debug_output, and report the actual output, including any errors. Stop it with stop_project when finished. Do not edit files.
What to look for

A run result, actual debug output, and a stop result. An empty console is not proof that gameplay works; check the scene yourself too.

Runs project code. Use a project you trust.

These are instructions for your local client. This page does not run tools or mark your connection as verified.

03

Know what you’re giving it access to.

Start with inspection. Running a project executes its code; editing scenes changes files. Keep a recoverable copy before edits.

Inspect

Read version and project information.4 tools
get_godot_version
Read the installed engine version.
list_projects
Find projects under a directory you specify.
get_project_info
Read a project’s metadata and structure.
get_uid
Read file UID information with the server’s Godot 4.4+ support.

Run & debug

Launches Godot and runs project code.4 tools
launch_editor
Open the editor for a project.
run_project
Start the project in debug mode.
get_debug_output
Read captured console output.
stop_project
Stop the project started by the server.

Edit scenes

Changes scene or resource files. Review the resulting diff.6 tools
create_scene
Create a scene with a chosen root.
add_node
Add a node with properties.
load_sprite
Assign a texture to a Sprite2D.
save_scene
Save a scene, including variants.
export_mesh_library
Export a 3D scene as a MeshLibrary.
update_project_uids
Resave resources to update UID references; requires the server’s Godot 4.4+ support.

How does this differ from an editor plugin?

The server in this guide runs as a separate process. Its tools can launch Godot and work with project files; they do not expose every editor action or the current selection. An editor plugin can use editor APIs, but its capabilities and version support depend on that plugin. Check its documented tool list before installing it.

MCP defines the connection between an AI client and a server. Using a local stdio transport does not mean the entire AI workflow stays offline: your assistant and package installer may still use the network.

Get unstuck

A connection is only
as useful as its next step.

Start with the actual error in your client’s MCP logs. Open the matching fix here.

Server issue tracker

The server does not appear

Check the configuration file belongs to the client and project you opened. JSON requires double quotes and no trailing commas. Enable or reload the server; restart the client if it has not picked up the change.

npx is missing or the server will not start

Check node --version and npx --version in a terminal. A desktop app may have a different PATH from your shell. Read its MCP error log and use the full executable path if needed. The -y argument accepts npm’s package-install prompt; the first launch needs access to the package registry.

Godot executable not found

Set GODOT_PATH to the absolute path of the executable, not the project folder or the enclosing .app directory. For JSON clients, add an env object inside the godot server entry; use forward slashes in Windows paths, or double each backslash for valid JSON. Restart the server after changing the environment.

Add this property inside the godot server object in JSON clients, replacing the example path:

"env": { "GODOT_PATH": "/absolute/path/to/godot" }

For Claude Code, use the server README’s command with --env GODOT_PATH=… before --.

The connection works, but the project tool fails

Supply an absolute folder path containing project.godot. Open that project in Godot directly to check it imports and runs. A working MCP connection does not fix missing assets, script errors, or an unset main scene.

I expected it to see my live editor selection

This guide uses Coding-Solo’s external-process server. It exposes the tools listed here, not a live editor-selection feed. If you need that, evaluate an editor plugin against its own tool list and supported Godot version.

A few common questions

How do I connect Claude to Godot?

Install Node.js 18 or later, add the godot-mcp server to Claude Code, Cursor or Cline (or Claude Desktop, using the Other clients config) with the command npx -y @coding-solo/godot-mcp, and set GODOT_PATH if the server cannot find Godot. Restart the client and ask it for your Godot version: a real version number means the connection works.

What is coding-solo/godot-mcp?

An open-source MCP server, published on npm as @coding-solo/godot-mcp, that runs outside the Godot editor. It gives an AI client tools to read project information, launch the editor, run a project and read its debug output, and create or edit scenes. It needs Godot and Node.js 18 or later.

What is MCP in Godot?

Model Context Protocol connects an AI application to tools exposed by a server. The community server used in this guide provides operations such as inspecting a Godot project, running it, and editing scenes. The assistant’s available actions depend on the server you install.

Does this page connect to my Godot editor?

No. This is a setup guide with copyable configuration and verification prompts. Install and configure the server in your own MCP client, then inspect its real tool results. This website cannot detect whether your local connection works.

Is this an official Godot integration?

The Coding-Solo godot-mcp server covered here is a community project. Check its README, requirements, and issue tracker for compatibility with your engine and client.

Is an agent file the same as an MCP server?

An agent file supplies instructions and coding conventions. An MCP server provides callable tools. You can use a Godot agent prompt without MCP, or combine the two; a prompt file alone cannot inspect or run your project.

Should I allow every tool automatically?

Start by reviewing calls and the project path they target. Running a project executes its code, and scene-editing tools write files. Keep a recoverable copy or version-control checkpoint before edits. The Cline example on this page leaves automatic approvals disabled.

Setup guidance reviewed against the server README and Claude Code, Cursor, and Cline documentation on September 8, 2026. The connection has not been run from this website.