A Godot MCP server is an editor plugin that exposes Godot's project data, scene tree, and scripting APIs as HTTP-callable tools following the Model Context Protocol standard. Claude Code and other AI clients connect to it so they can read and modify your game project directly, without copy-pasting context into a chat window.
Funplay MCP for Godot, maintained by FunplayAI, is the most complete implementation available today. Version 0.4.0, released on 2026-04-17, ships with 105 registered tools — the highest count in the four-repo Funplay MCP family. It runs as a GDScript addon inside any Godot 4.2 or later project, including Godot .NET (C#) projects.
Why This Matters for Claude Code Users
Claude Code works best when it has direct access to your project's state. A typical workflow without an MCP server goes like this: export a scene tree, copy it into your terminal, ask Claude Code a question, then manually apply the response back in the editor. That loop is slow and error-prone.
With Funplay MCP for Godot running, Claude Code can call tools directly. It reads node paths, inspects scripts, queries project settings, and returns results in one round trip. You stay in your terminal. The Godot Editor stays open on your other monitor. Neither side needs you to shuttle information between them.
The plugin is editor-only. It does not ship with your exported game, and it adds zero overhead to your build.
How It Works Under the Hood
The architecture is straightforward:
Claude Code (external AI client)
→ HTTP request to 127.0.0.1:8765
→ Funplay MCP addon (running inside the Godot Editor)
→ GDScript MCP server / tool dispatcher
→ 105 registered tools mapped to Editor and runtime APIs
→ Response sent back as JSON
The server listens on http://127.0.0.1:8765/ by default. If that port is occupied, the addon automatically picks a free port and saves the new value. The editor dock always displays the current endpoint so you can copy it into your AI client configuration.
Installation Walkthrough
Step 1: Add the addon to your project.
Option A — Clone the entire repository as a standalone Godot project and open it directly. Useful for testing.
Option B — Copy the addons/funplay_mcp/ directory into your existing project's res://addons/ folder:
# From your project root
cd my_godot_project
mkdir -p addons
cp -r /path/to/funplay-godot-mcp/addons/funplay_mcp/ addons/
Step 2: Enable the plugin in Godot.
Open your project in the Godot Editor. Go to Project → Project Settings → Plugins and enable Funplay MCP for Godot. A dock panel appears showing the server status and active port.
Step 3: Configure Claude Code.
Add the MCP server to your Claude Code configuration. The specifics depend on your setup, but the endpoint will be http://127.0.0.1:8765/.
Step 4: Choose your tool profile.
By default the plugin uses the core profile, which exposes a compact high-signal subset of the available tools. To access all 105 tools, open the Funplay MCP dock in the editor and switch the profile from core to full.
Language Awareness
The plugin detects your project's scripting environment and adjusts available tools accordingly.
- GDScript projects see GDScript-focused tools.
- Godot .NET (C#) projects see additional tools like
get_dotnet_project_infoand C#/.NET resource filters. - Mixed projects running both GDScript and C# see both sets of tools simultaneously.
This detection is automatic. You do not configure it manually.
Comparison Across the Funplay MCP Family
FunplayAI maintains four repositories, each targeting a different engine or purpose:
| Repository | Target | Tool Count |
|---|---|---|
| funplay-godot-mcp | Godot 4.2 or later | 105 tools |
| funplay-unity-mcp | Unity 2022.3 or later | 79 tools |
| funplay-cocos-mcp | Cocos Creator 3.8 or later | 67 tools |
| funplay-skills | Cross-engine | 12 skills |
Funplay MCP for Godot is the flagship repository with the highest tool count of the four. The Godot plugin's tool surface covers scene-tree traversal, resource inspection, script analysis, project settings queries, and more. The breadth matters because each additional tool reduces the chance that Claude Code hits a dead end mid-workflow and asks you to paste in context manually.
Supported AI Clients
One-click integration is available for five clients: Claude Code, Claude Desktop, Cursor, VS Code, and Codex. The knowledge base does not specify whether additional clients work through manual configuration, but any client that speaks the MCP protocol over HTTP should be able to connect to the local endpoint.
Gotchas and Limitations
No per-tool approval gate. Every exposed MCP tool runs directly when called. There is no confirmation dialog. The safety model assumes you trust the AI client running locally under your own control. If you are experimenting with agentic loops that chain many tool calls, test in a version-controlled project so you can roll back unwanted changes.
Editor-only. The server only runs when the Godot Editor is open. If you close Godot, the MCP endpoint goes offline and Claude Code will receive connection errors. This is by design — the plugin has no runtime component — but it means you cannot use it against a headless CI build server.
Local access only. The server binds to 127.0.0.1. Remote machines cannot reach it. This is a security advantage, but it means you cannot share one Godot instance across a team over the network without additional tunneling.
GDScript implementation. The plugin is written entirely in GDScript. It works in .NET projects because it calls Godot's editor APIs, not because it compiles C#. If Godot deprecates an editor API in a future version, the plugin needs an update to match. As of version 0.4.0, the requirement is Godot 4.2 or later.
Tool profile sizing. The core profile is the default for good reason: exposing all 105 tools to Claude Code increases context window consumption per request. If your task only involves inspecting a scene tree, the core subset is sufficient and faster. Switch to full only when you need the low-level tooling additions introduced in 0.4.0.
When Not to Use It
Skip this plugin if you are building a shipped, exported game — it has no runtime presence and provides no value there. Skip it if you do not use an AI-assisted coding workflow; the plugin does nothing without a connected client. And skip it if your project runs on Godot 3.x; the minimum requirement is Godot 4.2.
Closing
Install Funplay MCP for Godot from the primary repository, read more tutorials at gamebooom.ai/en/blog/, and explore sibling projects at funplay-unity-mcp and funplay-cocos-mcp.