Skip to content

Game development over MCP

By Eduardo Orellana · Updated

Most MCP writing is about the protocol. This is about the session — what an agent driving a game engine actually does, what it does not, and where the day goes. 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.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

The shape of a session

Two windows. Flockbay is open, showing your world and your game. Your agent is beside it, connected over MCP to the one server the app ships, which carries the capability layer, the assets and the game itself.

The first hour is not code. Start with a brief: agree with the agent what gets built first, what comes after and what is not in this version, before anything is built. Then it builds the scenes — the buildings, the props, terrain or water from a Godot plugin — as real nodes in the scene tree, in the editor you are watching. When one call is pure taste, exactly where the bridge sits, Godot's own editor is there in the Standard and Full views, and a drag is faster than a sentence.

Then the loop starts, and it is short. You ask the agent for behaviour. It writes GDScript into the project and plays it itself: input events in, stdout and the debugger out, a viewport capture to look at. Then you press Play, the game runs locally on the bundled Godot, and you decide whether it is right. Usually it is not right the first time, which is not a failure state — it is the loop working. You say what is wrong and go again.

More on this: How do AI game makers work?

Why a raw engine is a bad thing to hand an agent

Plenty of people have pointed a capable agent at a game project and been disappointed. The failure is rarely stupidity. It is that a game project does not describe itself. The meaning is spread across scenes, resources, node names and conventions nobody wrote down, so the agent reconstructs it from scratch on every turn and is subtly wrong in a different way each time.

Give it file-level tools and the problem gets worse rather than better. "Set property on node" is a keystroke, not an operation. An agent can execute a hundred of them correctly and still not have made anything, because none of them are at the level a game is described in.

So the useful work in MCP game development is not the plumbing. It is deciding what the operations should be. That is a design problem about games.

More on this: Making games with Ollama, and what that does not buy you

What the capability layer contributes

A capability earns its place when it collapses something the model would otherwise invent. Terrain of a given shape. Water that behaves like water. Weather, sky, characters and what they do. Each of those, once it is a real operation, is a body of code the agent never writes and a family of bugs that stops appearing.

The agent composes those operations instead of writing them, and it can run the game to check the result.

That is why Flockbay is described as a capability layer rather than an MCP wrapper around Godot.

More on this: Making games with local LLMs

Limits worth knowing before you start

The agent does not judge the game. It builds the scenes and can play them to check, and you can change anything yourself by hand in Godot's own editor, but whether it looks and plays right is decided by a person playing it. If you were hoping to describe a game in a paragraph and never look at it, this workflow will disappoint you.

Building needs an internet connection. Asset generation and your account come over the network, and that stays true whatever agent or model you are using and wherever it runs. Playing the finished game does not need a connection.

On Windows, Claude Code, Codex and Gemini CLI can install the Flockbay plugin from GitHub, flockbay/flockbay-plugin, which registers the server in one command, and the server is listed in the official MCP Registry. Any client that speaks MCP should be able to connect, we have not tested every one, and behaviour varies. The connection details live in the app and its docs rather than on this page, because published configuration goes stale and a wrong instruction is expensive.

More on this: Making games from Cursor

Requirements and cost

Flockbay is a desktop application for Windows, macOS and Linux. Godot ships inside it, so there is nothing else to install, and your project is a real Godot project in a folder on your disk rather than a file only this tool can open.

Connecting your own agent over MCP is free for your first build, and a plan keeps it building after that. The platform itself is free to start. What Flockbay costs has the detail. The engine underneath is the same open-source Godot either way.

And if you have no particular attachment to an outside agent, Flockbay's own AI ships in the app, agrees a brief with you before it builds, is already aimed at the capability layer, and requires none of this. It is the shorter path and there is no penalty for taking it.

Questions

What does MCP actually give me here?
A way for an agent you already use to call the capability layer, the assets and the game that the app serves over MCP, instead of Flockbay's own AI.
Can the agent make a whole game on its own?
It can build one: the scenes, the code as GDScript, and a play-test of its own work. It cannot decide whether the game is right. A person does that by playing it.
Do you have an integration with my agent?
For Claude Code, Codex and Gemini CLI on Windows there is the Flockbay plugin, flockbay/flockbay-plugin on GitHub, which registers the server in one command. Every other client connects over MCP directly, and that is the whole connection.
Where are the setup instructions?
In the app and its documentation. We do not publish configuration on pages like this because it goes stale without anyone noticing.
Is MCP access free?
Yes, for your first build: connecting is free, and a plan keeps it building after that. You pay your agent's provider for the model.
What runs the game?
The copy of Godot bundled inside the desktop app, locally on your machine. There is no streaming and no browser preview.

Free to download for Windows, macOS and Linux. One MCP server ships inside it.

Download Flockbay free