Making games from Cursor
To make games from Cursor, connect it to Flockbay over MCP: Cursor can then build, run and play-test a Godot 4 game in the editor Flockbay hosts. It can also open the same project as files, because it is a real Godot project on disk. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. It runs on Windows, macOS and Linux, on the official Godot engine.
The main page on this subject is Connect your own agent.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
The project is just files, which is most of the answer
Flockbay writes a real Godot project into a folder on your machine. Scenes, resources, GDScript. Nothing is stored in a proprietary format and nothing lives on a server you cannot reach. So the first and least exotic thing Cursor can do is open that folder and behave exactly as it behaves on any other codebase.
That already covers a lot of what people mean when they search this. Reading the code Flockbay wrote. Renaming things. Chasing a bug through three scripts. Adding version control and getting a diff you can actually review. None of it requires anything from us beyond the property that the output is an ordinary project, which it is.
It is worth saying that this path costs nothing extra and involves no protocol at all. If that is what you wanted, you can stop reading here.
The other path: driving the app over MCP
Flockbay ships one MCP server inside the desktop app, flockbay, and it carries Flockbay's scene tools and its library of ready-made models, textures and sounds to search and import. It also reaches the open Godot editor, where every edit is a step in Godot's undo, and the running game, which the agent can play-test. Cursor is an MCP client. That means an agent running in Cursor can call the same capability surface Flockbay's own AI calls, rather than only editing text in the project.
We should be blunt about what this is not. There is no official Cursor integration, no extension we publish, no marketplace entry. We speak MCP and Cursor speaks MCP. Any client that speaks it should work, these are the popular ones, and behaviour will differ between them. We have not tested them all.
Connecting your own agent over MCP is free for your first build, and a plan keeps it building after that. You pay your agent’s provider for the model. The app is free too, and so is your first build in it, AI included. What Flockbay costs has the detail.
More on this: Is there a Flockbay command line?
Editing files versus calling capabilities
The distinction matters more than it first looks. An editor-shaped agent sees a directory. It is very good at the things a directory affords: find the definition, change the call site, keep the types straight. It is much weaker at questions like whether the player still lands on the platform after a change, because a directory does not represent that, it only represents its consequences.
A tool call on the editor and the running game is the opposite. Flockbay's tools add a node through the Godot editor, which writes the scene file and its UIDs, then play the game, hold an input action and read Player.velocity back. Hand-edit a .tscn instead and a model will be wrong in a hundred small ways that each look reasonable in isolation.
So the useful mental model is that Cursor gets both surfaces, plus the game. The files for the code, the editor tools for the scenes, and the running game to play-test both. What it does not get is the last word on the calls that are pure taste. That is you, playing it.
More on this: Making games from Goose
What stays in your hands is the verdict
An agent in Cursor builds the scenes with the same tools Flockbay's own AI uses, in the project's kind, 2D or 3D, settled when it was made. In a 3D one that is the player controller, characters and props; in a 2D one, TileMapLayers and sprites; terrain, water or a sky come from a Godot plugin when the game needs them. Then it plays what it built: a headless run or a window, input events, stdout and the debugger with GDScript parse errors, a viewport capture.
Then you judge the result. You play the game and say whether it is right, and the agent changes it. That loop is normal work here, not a failure of the tooling. When the call is pure taste, where the wall sits or where that crate goes, drag it yourself in the Godot editor's own 3D or 2D view, and Ctrl⌘+Z takes a change back. A sentence gets you a layout; your hand can get you the exact layout.
If you want a fuller answer on what Flockbay is relative to an AI editor, and where the two ideas genuinely diverge, the Cursor for Godot page goes at it directly.
Practical shape of the setup
Flockbay is a desktop app for Windows, macOS and Linux. You download and install it, and Godot ships inside it, so there is no separate engine install and no browser version. When you press play the game runs locally on your machine, at your machine's framerate. Nothing streams.
Building needs an internet connection, because the AI and asset generation come over the network. That is true whether Flockbay or your own agent is driving. Playing what you already built does not need it.
The setup is at the end of this page. In the Flockbay app, Connectors, then Connect your agent (MCP), then Set up writes it with your own paths filled in, which is why you copy it from there rather than type it.
More on this: Making games from Gemini CLI
Connecting it is one paste
The Flockbay app writes this for you with the real paths filled in: open Connectors, press Set up on Connect your agent (MCP), 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.
Add it to %USERPROFILE%\.cursor\mcp.json on Windows, or ~/.cursor/mcp.json on macOS and Linux. Or press Add to Cursor in the dialog, which opens Cursor with the connection already filled in.
More on this: How to make games in Claude Code: from install to a game you can play
{
"mcpServers": {
"flockbay": {
"command": "<node>",
"args": [
"<coordinator>",
"--external-stage-mcp"
],
"env": {
"FLOCKBAY_MCP_DESCRIPTOR": "<descriptor>"
}
}
}
}Questions
- Can Cursor open a Flockbay project directly?
- Yes. It is a real Godot project in a folder on your machine, so any editor can open it. That path needs nothing from us and costs nothing extra.
- Is there an official Cursor extension?
- No. Flockbay ships one MCP server and Cursor is an MCP client. That is the whole connection. We do not publish an extension or maintain a listing.
- Do I need to pay to connect Cursor over MCP?
- Not for your first build. Your first build is free, on Cursor over MCP or on Flockbay's own AI inside the app, and a plan keeps you building after that. You pay your agent’s provider for the model.
- Should I use Cursor instead of Flockbay?
- If you already work in Cursor and want to stay there, it is a reasonable choice. Flockbay's own chat in the app needs no setup and already knows the project conventions, so it is usually the faster start.
- Can an agent in Cursor build the level for me?
- Yes. It builds the level and plays it to check it. The level is yours to judge: play it, then say what to change, or make a taste call by hand in the Godot editor.
- Does any of this work offline?
- No. Building needs a connection for the AI and asset generation. Running a game you already built does not.
Free to download for Windows, macOS and Linux. Connecting your own agent over MCP is free for your first build, and a plan keeps it building after that.
Download Flockbay free