Making games from Cline
Cline is an open-source agent you run yourself with your own model key. Flockbay ships an MCP server inside the desktop app. Point one at the other and your agent can call the same capability layer Flockbay's own AI calls. 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.
One bill to start, and it is your model's
People who choose Cline usually chose it on purpose: it is open source, it runs in an editor they already have, and they supply their own model key so the model cost is theirs to see and control. That is a coherent position and we are not going to argue you out of it.
It does mean you should know what connecting to Flockbay costs on our side. Connecting your own agent over MCP is free for your first build, and a plan keeps it building after that. What Flockbay costs has the detail.
What Cline reaches is not a different engine, a reduced tool set or a lesser version of the capability layer. It is the same one Flockbay's own AI calls.
More on this: Making games with Ollama, and what that does not buy you
The connection is the protocol, nothing more
There is one MCP server inside the Flockbay desktop app, flockbay, 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. Cline is an MCP client. Both sides implement the same protocol, so they can talk. That is the entire integration story and we would rather state it flatly than dress it up.
We do not publish a Cline extension, we do not maintain a listing, and there is no partnership. Any client that speaks MCP should work. These are the popular ones people ask about, we have not tested each of them, and behaviour will vary.
The setup is at the end of this page, and the connection guide covers the rest. 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: AI agents and game development
Plan first, then act, and why the grain of the tools matters
Agents that separate planning from execution are only as good as the vocabulary they plan in. A plan written as raw text edits to .tscn files reads as a list of keystrokes, tells you nothing about whether the result will be the game you wanted, and one wrong resource ID breaks the scene.
Flockbay's tools plan in Godot's own terms, and each plan ends in a check. A step reads "instance res://props/crate.tscn under Level", "attach player.gd to Player and connect body_entered", then "play, hold jump for 0.3 seconds, capture the viewport, read Player.velocity". A plan written in those terms is a plan you can read and disagree with before anything happens, which is the point of having one. Flockbay's own AI works that way too: a brief of what gets built first, what comes after and what is not in this version, approved before anything is built.
It also cuts the amount the model must invent. The editor writes the scene file, its UIDs and the undo step, so the model composes against code that already works rather than writing it from nothing. That is why the tools matter more than which model you pointed at them.
More on this: Making games from Gemini CLI
The judgement does not come over the wire
Cline builds the scenes through the same tools Flockbay's own AI calls, as real nodes and resources in the scene tree: the player controller, characters and props, TileMapLayers and sprites in a 2D project, with terrain, water or a sky from a Godot plugin when the game needs them. Then it plays what it built: it runs the game headless or in a window, sends input events, reads stdout and the debugger, GDScript parse errors included, and captures the viewport. A jump that never leaves the ground reaches Cline before it reaches you.
What it cannot do is decide whether the game is right. You play it, you dislike something, you say so. When the thing you dislike is pure taste, where the crate sits or which way the path bends, 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. That loop is the normal way to work here, and nothing about bringing your own agent changes who the judge is.
If shuttling between an editor and the app sounds like friction you did not want, using Flockbay inside the app is a completely reasonable answer, and it needs no setup at all.
What you are actually installing
Flockbay is a desktop application for Windows, macOS and Linux. Downloaded, installed, with its own copy of Godot inside it. No browser version, no hosted editor. The project it works on is a real Godot project in a folder on your machine, so your agent operates on files that exist and version control behaves normally.
When you press play, the game runs locally on the bundled Godot at your machine's framerate. Nothing is streamed and nothing is rendered somewhere else.
Building needs an internet connection. The AI and asset generation come over the network, and that is true no matter whose agent is driving. Playing a game you already built does not need it.
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 Cline 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.
In Cline, open MCP Servers, then Configure, then Configure MCP Servers, and add it to the file that opens.
More on this: Making games from OpenCode
{
"mcpServers": {
"flockbay": {
"command": "<node>",
"args": [
"<coordinator>",
"--external-stage-mcp"
],
"env": {
"FLOCKBAY_MCP_DESCRIPTOR": "<descriptor>"
}
}
}
}Questions
- Is connecting Cline 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.
- Is there a Cline extension for Flockbay?
- No. Flockbay ships one MCP server and Cline is an MCP client. We do not publish an extension or maintain a listing anywhere.
- Which model should I use with it?
- That is your call. Any model Cline runs works over MCP, and every one gets the same tools, including running the game and reading its errors.
- Can the agent do the level design?
- Yes: build the scenes, set up the player controller and place props, add terrain, water or a sky from a Godot plugin, then play the result to check it. Whether the level plays well is yours to judge, and any of it can be moved by hand in the Godot editor.
- Do I need Godot separately?
- No. Godot ships inside the Flockbay desktop app on Windows, macOS and Linux.
- Will this work offline if my agent runs locally?
- No. The AI and asset generation come over the network, so building needs a connection regardless of where the model runs. Playing what you 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