Skip to content

Making games from Goose

By Eduardo Orellana · Updated

Goose is built around MCP and is deliberately model-agnostic. Flockbay ships one MCP server inside the desktop app, so it can appear as one more thing your agent knows how to call, next to everything else you already gave it. 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.

Download for macOSDownload for WindowsDownload for Linux

One more server among the ones you already have

The way Goose is put together makes this straightforward to picture. You add capabilities by adding servers, and the agent works out what it can call. Flockbay ships one of them 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.

That means the game engine does not have to be a separate world you switch into. It can sit beside whatever else you have connected, and an agent can move between them in a single piece of work. Pull a reference from somewhere, put something into the project, come back. Nothing about the protocol prevents that.

We should say what this is not. There is no Goose extension we publish and no partnership; the server's one listing is the official MCP Registry. We speak MCP, Goose speaks MCP. Any client that speaks it should work, and we have not tested every one, so expect behaviour to differ.

More on this: Making games from Cursor

Model-agnostic is the interesting part

Goose lets you swap the model underneath, and whichever you pick, it does better work against a game engine when it has less of the game to invent.

Point an agent at a bare Godot project and it must invent almost everything: how a scene is meant to be structured, what belongs where, what a .tscn file's resource IDs and UIDs must say, and which node a script expects at which path. Every one of those is a guess.

Flockbay's tools remove most of the guess. The editor writes the scene file, its UIDs and the undo step, and the agent runs the game and reads stdout to see whether the change worked, so the model composes against code that already works instead of writing it from nothing.

More on this: What is MCP for game development?

Where composing across tools stops helping

It is worth tempering the appeal of a single agent that can reach everything. Connecting more servers gives an agent more to consider on every turn, and the practical effect is often a slower, less decisive agent rather than a more capable one. If a session is about the game, a narrow set of tools tends to go better.

The other limit is the one that does not move: judging the game is yours. Goose builds the scenes, props and characters in a 3D project, TileMapLayers and sprites in a 2D one, with terrain, water or a sky from a Godot plugin, and can play the game to check its work, but you are the one who looks at the result and decides. When the call is pure taste, exactly where the crate sits or which way the path bends, drag it yourself in the Godot editor's own 3D or 2D view: for that one change a sentence is a worse instrument than your own hand.

And you are the one who says whether the game is right. You play it, you find what is wrong, you go back in. That loop is the normal shape of the work here.

What it costs and what it needs

The Flockbay download is free, your first build included, and Flockbay's own AI in the app is free to start: hosted AI, or your own Claude or ChatGPT. Connecting your own agent over MCP is free for your first build, and a plan keeps it building after that. The engine is the same either way.

Flockbay is a desktop application for Windows, macOS and Linux. It is downloaded and installed, with its own copy of Godot inside it, so there is no separate engine to set up and no browser version. The project is a real Godot project in a folder on your machine, which is why an agent can work on it at all.

Building needs an internet connection, because the AI and asset generation come over the network. That is true whether the model is running on your machine or somewhere else. Playing a game you already built does not need it.

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

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 Goose 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 ~/.config/goose/config.yaml, under the extensions you already have.

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

YAML
extensions:
  flockbay:
    name: flockbay
    type: stdio
    cmd: '<node>'
    args:
      - '<coordinator>'
      - '--external-stage-mcp'
    envs:
      FLOCKBAY_MCP_DESCRIPTOR: '<descriptor>'
    enabled: true
    timeout: 300

Questions

Does Goose work with Flockbay?
Flockbay ships an MCP server and Goose is an MCP client, so it should. We have not tested every client and behaviour varies between them.
Is there a Goose extension for it?
No Goose extension of ours. Goose adds Flockbay the way it adds any MCP server, and the server is listed in the official MCP Registry as io.github.flockbay/flockbay. The connection is the shared protocol and nothing else.
What does it cost?
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.
Which model should I run underneath?
Your choice. Any model Goose runs works over MCP, and every one gets the same tools, including running the game and reading its errors.
Can the agent build the levels?
Yes. It builds the scenes, sets up the player controller and places props, adds terrain, water or a sky from a Godot plugin, then plays the game to check. You judge the result, and the Godot editor is open beside it if you want to move something yourself.
Is Flockbay open source?
No. Flockbay, the capability layer and the app on top of it, is closed source. Godot underneath is open source under the MIT licence, and your project is a real Godot project.

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