A guide to Godot MCP servers: install, connect, and use one well
3 min read
By Eduardo Orellana ·
A Godot MCP server takes about two minutes to install and changes how an agent works with your game: it can run the project and read the errors itself. Here is the install, the first tasks to try, and the habits that avoid lost work.
Install one
The full guide, with the setup for Claude Code, Codex, Cursor and other agents, troubleshooting and a comparison of servers, is the Godot MCP guide.
The free godot-mcp by Coding-Solo installs with one command in Claude Code: claude mcp add godot -- npx @coding-solo/godot-mcp. In Cursor or Cline, add it to the MCP settings with the command npx and the argument @coding-solo/godot-mcp.
Paid servers such as GDAI MCP install as a Godot plugin plus a client entry; follow their own setup page, since it changes between versions.
More on this: Claude or ChatGPT for Godot
First tasks to try
Ask the agent to report the Godot version and list the project's scenes. Then ask it to run the game and tell you what the output says. Those two confirm the connection works.
Then give it a real task with a check: "fix the error in the output and run the game again".
Habits that avoid lost work
Commit to version control before each session. If a server writes scene files straight to disk, close the Godot editor first, or a save from the editor can overwrite the agent's changes. A server that edits through the open editor, as Flockbay's does, avoids that: each change is one Ctrl+Z.
Keep tasks small, and play the game yourself after each one.
More on this: Connect your own agent
Connecting an agent to Flockbay
Flockbay has its own MCP connection, free with a Flockbay account. In the app, open Connectors, press Set up on the Another agent (MCP) row, press Turn on, and copy the ready-made line for your agent. The commands contain paths specific to your machine, which is why the app gives them to you.
Your agent then gets the open Godot editor with undo, the running game to playtest, and six world tools: terrain, water, environment, weather, the player controller and props. Turn off ends it at any time. The full setup is in the Godot MCP guide.
More on this: Making games with Kilo Code and Flockbay
Troubleshooting
If the agent cannot find the tools, restart the agent after adding the server. If it finds them but calls fail, check the server's own logs and your Godot path. If results look wrong, check the Godot version the server expects.
More on this: How to make games in Claude Code: from install to a game you can play
What to ask for once it works
Useful: "run the game, find any errors, and fix the first one." "Add a node that shows the player's speed on screen for debugging." "List every script that references the player."
Less useful: large creative requests with no check. Servers shine when the agent can verify its own work.
What a server does not give you
Taste. The agent can make the game run; you decide whether it is right. That split is the same for every server.