Making games from Gemini CLI

A capable agent pointed at a Flockbay project can read all of it. The project is a real Godot project in a folder on your machine, in ordinary text formats, so there is nothing to unpack and nothing hidden. Ask what a script does and you will get a decent answer.

That feels like most of the problem solved and it is not. Understanding a project tells you what is there. It does not tell you what should be there, and it does not give you a safe way to put it there. An agent that has read every file still has to decide how to express a change, and in a bare game project the only vocabulary available is fine-grained: create a node, set a property, write a script.

Those are keystrokes, not operations. A model composing at that grain can be wrong in a hundred small ways that each look reasonable when you inspect them one at a time.

Flockbay ships one MCP server inside the desktop app, and it carries the capability layer, the assets, and the game itself, which it can edit in the open Godot editor, run, look at and play. The layer is a set of operations at the level a game is actually described in, and it comes in two sets, because creating a project asks whether the game is 2D or 3D. In a 3D world: terrain of a given shape, water following an outline, weather, sky, characters and what they do. In a flat one: a tile ground that works out its own edges and its own collision from the cells you covered, one band of scenery along the horizon, a person whose walking and jumping are values you set rather than code somebody writes, and sprites placed at an exact position, turn and size.

Each capability is a body of code that already exists and already works, which means it is a body of code the model does not have to invent. That is the whole bet. Less invention means fewer failures, and it means a cheaper model composes reliably where a bare project would have required an expensive one just to keep the plausible mistakes down.

So the interesting difference is not context size or how much of your project an agent can hold at once. It is whether the surface it is calling was designed for games or is just the engine's internals with a protocol taped on.

More on this: How do AI game makers work?

Worth being direct, because the low entry cost is often exactly why people picked this tool. Connecting your own agent over MCP is free. The platform itself is free. Whatever your agent costs you is separate and unrelated.

The Flockbay download is free and so is the whole builder, and Flockbay ships inside the app, free on your own AI: your Claude or ChatGPT plan, your own agent, or an API key.

Or pick a plan and Flockbay runs the AI for you. Flockbay builds from a library of ready-made objects, or with Godot's own shapes. There is no better engine, builder or capability layer to pay for.

More on this: How to make games in Codex: the Codex CLI, the ChatGPT app, or your ChatGPT plan inside Flockbay

We have not built anything specific to Gemini CLI. We speak MCP; it speaks MCP. There is no extension we publish, no listing, no partnership. Any client that speaks the protocol should work, and the ones people ask about are simply the popular ones. We have not tested them all and behaviour varies.

The setup is at the end of this page. The Flockbay app 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 Cline

You shape the world by hand with the builder, a set of tools around the Godot editor's own 3D and 2D view — terrain, water, weather, buildings and characters in a 3D project, painted tile ground and sprites out of a Catalogue that runs to 55,073 of them in a 2D one, placed and looked at either way. That is where taste is the input. A connected agent can call the same world tools, but judging what they made stays with you.

You also judge. You play the game, decide what is wrong, and go back in. That loop is the normal work here rather than a sign the tooling failed. Not writing the code has never meant not having an opinion about the game.

Flockbay itself is a desktop application for Windows with Godot inside it. Games run locally when you press play. Building needs an internet connection because the AI, asset generation and world data come over the network; playing what you already built does not.

The Flockbay app writes this for you with the real paths filled in: open the account menu, choose MCP connection, press Turn on, pick Gemini CLI 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 ~/.gemini/settings.json, next to anything already under mcpServers.

More on this: Is there a Flockbay command line?