Cursor for Godot: how to use Cursor on a Godot game, and let it run the game too

People who search for a Cursor for Godot usually want one of two things. Some want Cursor itself, the AI code editor, pointed at a Godot project: an agent that reads the whole project, makes multi-file edits and explains a bug. Others want a Cursor-shaped tool made for Godot, where the AI also understands scenes, nodes and the running game rather than only text.

The first exists and works well, with one gap. Cursor sees files. A Godot game is files too, until you press Play, and from then on Cursor is blind: it does not know the player fell through the floor. Everything below is about closing that gap, first with Cursor alone, then with a Godot MCP server, then with Flockbay.

In Cursor, open the folder that holds project.godot. That is the whole project: scenes as .tscn, resources as .tres, scripts as .gd, all text. Leave the .godot folder alone; it is Godot's import cache and rebuilds itself.

Install godot-tools from the Extensions panel. Cursor installs extensions from Open VSX, where geequlim's godot-tools is listed, version 2.7.1 as of 29 Sep 2026, MIT licensed. It gives GDScript highlighting and, while the Godot editor is running, completions and go-to-definition from Godot's own language server, which listens on port 6005 by default.

If you want Godot to open scripts in Cursor rather than in its own script editor, set Cursor as the external editor in Godot under Editor, Editor Settings, Text Editor, External.

One trap: if a script is open in Godot and Cursor changes it on disk, Godot asks whether to reload it. Answer Reload. Saving Godot's copy writes the old text over Cursor's change.

Models have read a lot of Godot 3 code, and it shows: yield where Godot 4 uses await, KinematicBody where it is CharacterBody3D, export var where it is @export. One project rule fixes most of it.

Project rules live in .cursor/rules as .mdc files, each with a short header that says when it applies: always, by file pattern, when the agent judges it relevant, or only when you mention it. A plain .md file in that folder is ignored. For something short, an AGENTS.md at the project root does the same job. User Rules, under Customize, then Rules, apply to every project.

Put in the rule what the agent would otherwise guess: the Godot version, typed GDScript, where the main scene is, what not to touch, and a check it can run. Godot does a headless run and quits after a set number of frames when given --headless --path . --quit-after, printing every error to stdout; on Windows use the Godot executable whose name ends in _console.exe so the output reaches the terminal.

More on this: The best AI for GDScript: what good output looks like

It can read and change every script and scene, rename a signal across twelve files, write a state machine for an enemy, and explain why a node path is null. With the rule above and your permission, it can boot the game headless and read the errors. That is a lot, and for a programmer it is most of what the search promised.

It cannot see the game or play it. It does not know the camera is pointing at the sky or that the jump feels floaty. It cannot press a key in your game. And it is guessing when it hand-edits a .tscn file, which carries resource IDs and UIDs the Godot editor would have written for it.

Cost: Cursor's Hobby plan is free with limited agent requests. Pro is $20 a month, Pro Plus $60 and Ultra $200, as of 29 Sep 2026. You can also bring your own OpenAI, Anthropic or Google key for chat models, under Cursor Settings, then Models. Godot is free.

More on this: The best AI coding assistant for Godot is the one that knows Godot 4

MCP is how Cursor is handed tools beyond files. A Godot MCP server runs the game for Cursor and hands back what Godot printed, so the agent fixes an error it saw rather than one you pasted. Cursor reads servers from mcp.json: ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one. You manage and switch them on and off from the Customize page. Cursor asks for approval before it uses an MCP tool unless you change that.

Coding-Solo's godot-mcp is free and MIT licensed: it launches the editor, runs the project in debug mode and captures the output, and creates scenes and nodes. Its README mentions no screenshots and no input. GDAI MCP, $19 once, and Godot MCP Pro, $15 once, plug into your own Godot editor and add screenshots and simulated input. All three work on a Godot project you already have. The detail is in the best Godot MCP server.

More on this: The best AI for Godot depends on whether you want to write code

Flockbay is a free AI game maker built on Godot: a desktop app with the official Godot 4.7.2 inside, not a fork. Your game is a real Godot 4 project you can open, read and change, and the builder lives inside the Godot editor, as buttons around its 3D and 2D view. Connecting Cursor to it is free, and it turns Cursor from a file editor into something that works on the running game.

In the Flockbay app, open your game, then Connectors from the Flockbay menu. Press Set up on the Another agent (MCP) row, press Turn on and pick Cursor. Press Add to Cursor and Cursor installs the server itself, or press Copy and add the block to ~/.cursor/mcp.json, which on Windows is %USERPROFILE%\.cursor\mcp.json. It is one server, flockbay-stage. Install skills and hooks, in the same place, gives Cursor Flockbay's instructions and a hook that asks it to play the game before it calls a change done.

The Flockbay app writes this for you with the real paths filled in: open the account menu, choose MCP connection, press Turn on, pick Cursor and press Copy. The three paths are specific to your machine and stay the same from one sitting to the next, so you paste it once. Below is the shape, with the paths as placeholders.

Edit through the Godot editor with undo. Adding a node, setting a property, writing a script, connecting a signal: each change is one step in Godot's own undo history, so Ctrl+Z in the editor takes it back.

Run the game and read it. Cursor plays the game in the app's Game screen and reads its stdout, with every error's file, line and call stack. It can also do a headless run to check that it starts.

Playtest. It injects timed input events (keys, mouse motion, InputMap actions) into the running game, reads values off the live scene tree such as the player's velocity, and captures the game and editor viewports. Your real keyboard and mouse are never touched, and pressing a key yourself stops its input at once.

Build the world. Terrain, water, sky, weather, the player controller and props are whole systems Cursor calls rather than writes: six families in a 3D world, four in a 2D one. It can bring in models, textures and sounds from Flockbay's library, or generate them on your own Tripo or ElevenLabs key.

You still judge the result. Press Play or F5 in the editor and play it; its numbers say what happened, not whether it was fun. Its work shows in the app in a chat named Your agent, and Flockbay never starts the game under you while you are using the builder.

Connected to Flockbay, Cursor closes the agent loop on the running game, not only on the code. It validates every GDScript file without running it, starts a Play or a headless run, injects a timed sequence of input events (keys, mouse, InputMap actions, up to 200 steps), captures the game viewport, and reads the live scene tree, stdout and the debugger's errors with file, line and stack. Then it changes the code and plays again. Flockbay's own AI runs that check, play, read, fix loop by itself; your own agent gets the same tool calls over MCP, free.

What it does not do: play a whole game through to a goal, return a pass or fail verdict, keep a regression suite, record video, file bug reports, run parallel instances, or judge balance and feel. Human playtesters still decide whether the game is fun.

The connection reaches the game Flockbay has open, which can be a Godot project you already have: Flockbay asks before it adds anything to it. To keep your existing project in your existing editor, Cursor with one of the servers above is the better setup.

The Flockbay app runs on Windows today, and the Mac release comes later. It needs an internet connection while you build; the game plays offline. New code is GDScript, or C# when the game already uses it. Flockbay is closed source.

If you want Flockbay's own chat instead of Cursor's, it runs free on your Claude plan, a ChatGPT sign-in on Plus or higher, or your own API key. What Flockbay costs has the detail.

Summer Engine describes itself as a Cursor-like editor built around AI that opens your existing Godot 4 project. It is a desktop app for macOS on Apple silicon and Windows, built on Godot 4.7.2, and its own site calls it a fully custom engine with more than a million lines of custom code.

It also ships a free, MIT-licensed MCP server for Cursor and other agents, installed with npx -y summer-engine@latest setup cursor --yes. Its page says an outside agent can run the game, read its errors, send it input and take screenshots; the tools drive the Summer Engine app, which has to be open with the project loaded. Its plans are $20, $60 and $200 a month, and connecting over MCP is free. If you are on a Mac today, it covers ground Flockbay does not. Our side-by-side is Flockbay vs Summer Engine.

More on this: Summer Engine alternatives in 2026: seven real options, and when to stay

No completions in GDScript. godot-tools gets them from the Godot editor's language server, so Godot has to be running with the project open. Check that the port in the extension's settings matches Godot's, 6005 by default.

The MCP server does not appear. Open the Customize page and check it is listed and switched on. If you edited mcp.json by hand, check it is valid JSON, and that it is the global file or the one in the folder Cursor has open.

Flockbay's server lists a single tool. The Flockbay app is not serving Cursor yet: open the app, open your game, and turn on Another agent in Connectors. The tools then appear by themselves; if they do not, start a new chat in Cursor.

Cursor keeps asking before each tool. That is Cursor's default for MCP tools. Its run modes decide what runs without asking.

A change you cannot see in the game. Stop the game and press Play again; a running game does not reload a change on its own.