Flockbay vs Summer Engine: official Godot, or an engine built on it

Both are desktop apps where an AI builds the game and you play it, and both start from the same place: Godot 4.7.2. What happens after that is the whole difference.

Flockbay bundles the official Godot 4.7.2 release, not a fork. The AI writes GDScript and scenes into a real Godot 4 project on your own disk. Stock Godot 4.7.2 opens the same folder, and you can read and change every file there or in your own code editor, with the Godot docs and your version-control habits as they are.

Summer Engine says its engine is "built on the Godot 4.7.2 foundation" and, in its own words, "a fully custom engine at this point, with more than a million lines of custom code". It says it always follows Godot upstream and "stays backward compatible with Godot". Its changelog lists rendering, input and editor fixes of its own, and exported games run on its own export templates. That is real engineering, and it also means your game depends on Summer's build of the engine rather than Godot's.

More on this: Cursor plus Godot vs Flockbay: two ways to make a Godot game with AI

Flockbay opens your game in the Godot editor. The chat sits in a dock, and the builder is a row of buttons around the editor's own 3D and 2D view: Sculpt, Paint, Plants, Place, Water, Sky, Weather, Characters, People and Camera in 3D, and Paint, Place and Characters in 2D. They act on the live world, and Godot's own undo takes a change back. The app's Game screen only plays, and every Play is a fresh run.

Summer puts its AI in its own editor: "Summer AI lives in the desktop app." Its Design Mode lets you click nodes or draw on the 2D and 3D viewport to tell the AI what to change.

Flockbay keeps the whole editor: Godot's docks, main menu, Script editor and Asset Store, with Godot's own run bar put away because Play is the app's. A Simple editor, one switch away, leaves only the view, the builder and the chat.

Flockbay speaks MCP, so Claude Code, Codex, Cursor or any MCP client can build the game you have open. It is one server, registered as flockbay-stage. It is free with a free Flockbay account; you pay your agent's provider, as you already do.

Your agent gets what Flockbay's own AI gets. It can shape the world through the same controls you have: terrain, water, sky, weather, the player controller and props (four of them in a 2D world). It can edit the game through the open Godot editor, with undo. And it can playtest the game: run it, read stdout and errors, capture viewports, inject input events, and read and change the live scene tree.

In the app, Connectors, then Another agent, then Set up writes the line with your machine's paths filled in, and you paste it once. For Claude Code it has this shape, with the three paths as placeholders:

More on this: The best Godot MCP server in 2026 depends on what you want the agent to touch

Summer says "MCP is free", and its docs include local MCP on every plan. Its setup is public commands you can read before you run them: install, login, then npx -y summer-engine@latest setup <agent> --yes, which writes the MCP config and installs Summer's game-dev skills. Its MCP page counts 86 tools, and its pricing lists "MCP skills and hooks" on Pro+, the $60 plan. That installer is a real strength: Flockbay's line comes from the app, and there is no public Flockbay CLI.

Flockbay also runs its own chat on your Claude plan (Pro or Max), a ChatGPT sign-in (Plus or higher) or your own API key (OpenAI or Anthropic), free. Summer's docs say it "does not accept your own provider API keys for hosted generation"; your own model reaches Summer through MCP.

More on this: The best AI tools for Godot in 2026, with a verdict on every one

Flockbay's plans are Indie at $20, Pro at $60 and Ultra at $200 a month. Each opens a band of hosted models chosen by what they cost to run: fast, low-cost models on Indie, stronger models on Pro with 3× Indie's usage, nearly every model on Ultra with 10×. The most expensive models, like GPT-5.5 Pro, are on no plan and run only on your own key. A plan also generates pictures and sound; 3D models are made on your own Tripo key. Every new account gets Demo, a small free allowance on a small, low-quality model, and building on your own AI stays free. What Flockbay costs has the details.

Summer's plans are Pro at $20, Pro+ at $60 and Ultra at $200 a month; yearly billing saves 20%, and a $5 Basic plan is offered inside the app. Past a plan's limit you can add on-demand usage "at the same API rates". Its free tier reads "Try hosted Summer AI when you create an account".

In Flockbay the game runs on your computer, on the copy of Godot the app brings with it; nothing is streamed. Building needs an internet connection, because the AI, generation and world data come over the network. Playing what you built does not. When the game is ready, you can publish it to Steam directly through Flockbay.

Summer's MCP tools include playing and stopping the game, screenshots, the console and debugger errors, and it exports desktop builds for Steam or itch.io.

More on this: Claude for Godot: how to build a Godot game with Claude Code, step by step

Flockbay runs on 64-bit Windows today; the Mac release follows later. It is online only while you build. It is closed source: the app, the builder and Flockbay's instructions are ours, while the engine is Godot and your project is yours. C# runs too: the .NET tools download the first time a game uses C#, and new code is GDScript unless the game is already C# or you ask for C#.

Summer ships on macOS and Windows today, writes C++, GDScript and C#, and publishes its CLI, skills and hooks under MIT on GitHub, along with its game templates. Its engine source is not published.