# Flockbay > Flockbay is the Godot editor with an AI agent and an MCP server built in. Compatible with Godot 4.x. A free AI game maker built on Godot: it builds and play-tests your game on free AI to start, your own Claude or ChatGPT, or your own agent over MCP. - A plain Godot 4 project on your own disk, on the official engine, not a fork: it opens in stock Godot. - No royalties, and no share of your sales. - Your project stays on your machine. Nothing uploads it unless you publish it to your own GitHub or share a playtest build. - Works with Claude Code, Codex, Cursor and any MCP client, through one MCP server registered as `flockbay`. Connect your agent: on Windows, after installing Flockbay, run `claude mcp add --scope user flockbay -- flockbay mcp` or `codex mcp add flockbay -- flockbay mcp` in a new terminal; any other MCP client runs the command `flockbay mcp`. On a Mac or Linux, Connectors › Connect your agent (MCP) › Set up › Turn on in the app writes the line for your machine. An agent can set itself up from the setup prompt: https://flockbay.com/docs/agent-setup-prompt.md On Windows, Claude Code, Codex and Gemini CLI can also install the Flockbay plugin, which registers the same server: `claude plugin marketplace add flockbay/flockbay-plugin`, then `claude plugin install flockbay@flockbay` (https://github.com/flockbay/flockbay-plugin). The server is listed in the official MCP Registry as `io.github.flockbay/flockbay`. **Flockbay** is the company, the website and the desktop app you download. There is one name and nothing else to call it. The AI you talk to in the app carries the same name: you say what the game should be, it agrees a brief with you, and once you approve it, it builds the world, writes GDScript and scenes into your project, and plays the game to check its work. Under it is [Godot](https://godotengine.org), the official release, bundled with the app; Flockbay works with Godot 4.6+. Between the two is Flockbay's capability layer, which makes a Godot project operable by an AI. Key facts: - **It is an AI game maker built on Godot.** The AI writes GDScript and scenes into a real Godot 4 project on your own disk: levels and props, behaviours, systems, rules, states. Nothing is built until you approve its brief: what comes first, what comes after, and what is not in this version. It is not a chat box that returns a finished web game, and not a fork of the engine. The code lands in a project you keep, and you can read and change every file in stock Godot or your own code editor. - **Who it is for.** Developers who build games with AI, first. You can bring the agent you already use, read the code and change it. You do not have to write code, and the creator always judges the result by playing it. - **Platform:** Windows, macOS and Linux. On Windows it runs on 64-bit Windows with an Intel or AMD processor. Linux is an x86_64 AppImage for Ubuntu 22.04, Debian 12, Fedora 39 or newer (glibc 2.35), on the distribution's GTK 3 and WebKitGTK 4.1, with no ARM build; an Intel or AMD Chromebook with Linux turned on runs the same AppImage. On a Mac it is the same app, for Apple Silicon and macOS 15 or later, with no Intel Mac build. There is no web version, no browser editor, no browser preview, and no mobile app. - **Flockbay hosts the full Godot editor.** The Scene dock, Inspector, FileSystem, Script editor, Asset Store, main menu and bottom panel are Godot's own; only Godot's run bar is put away, because Play is the app's. Every project opens in Minimal view, the chat and the Game screen, until you choose another. Standard view keeps the main menu, the Scene and Node docks, the Inspector, FileSystem, the Script editor, the scene tabs and the bottom panel, and puts away the Asset Store, Import and History; Full view is all of Godot's editor. - **Your hands are in Godot's editor.** Change anything by hand with Godot's own tools, and Godot's own undo takes it back. The chat sits in a dock in the same editor. The app's Game screen only plays, and every Play is a fresh run. - **2D or 3D is settled when you create a project.** The answer is read from your description of the game and confirmed before anything is created. Every game starts blank: the world is the first build of the brief you approve. - **Plugins from the Godot Asset Store.** Terrain, sky, water, a character controller or any other system comes from a Godot plugin, or from nodes and scripts the AI writes. The Plugins panel lists the free add-ons on the Godot Asset Store whose scripts load on the Godot the app runs and that fit the open project, with publisher, licence, version and the autoloads and input actions each adds; Install puts one in the project and enables it. Flockbay's AI can find one and offer it in the chat, and installing it is your press. - **Side-on and top-down are not separate 2D modes.** The AI writes the player controller the brief calls for: with gravity, down is a direction and a jump is available; without it, the character steers on both axes. - **The AI playtests the game.** Flockbay's AI, and your own agent over MCP, can edit the game through the open Godot editor with undo, run it, read stdout and errors, capture viewports, inject input events, and read and change the live scene tree. - **Art:** the Catalogue is 90.8% sprites — 55,073 of 60,648 objects — searchable by name with a picture of each, downloaded into the open project on demand. Pictures and sound (effects, loops and music) are generated on the free hosted AI or a plan's usage, or on your own keys. The AI builds 3D models on your computer with no key; Tripo 3D generation uses your own Tripo key. Godot's own shapes are always there. You can import your own files from your computer. - **Output is a normal Godot project** in a normal folder on local disk. It opens in stock Godot. - **Games run locally** on the copy of Godot bundled with the app, or on your own Godot for a project you keep on another version. No streaming, no cloud rendering, no render queue. - **Export:** Publishing tools › Export builds the game for Windows, macOS, Linux or the Web from the project's export presets, as a release or with Export With Debug. A Windows release is one .exe with the .pck embedded; a macOS release is an .app, in a .zip when exported from Windows; Linux (the .x86_64 and its .pck) and the Web (index.html with its .wasm and .js, for a web host or itch.io) are Godot's own export, written into a folder. Export in Godot… opens Godot's own Project › Export… for Android, iOS and anything else Godot exports. Builds are unsigned unless the preset signs them. - **Building requires an internet connection.** No sign-up stands in front of it: a new install builds on a guest account the app makes for itself. The chat and asset generation cross the network. Playing the game you built does not. There is no offline mode. - **Pricing:** Free to start, AI included. Every account, guests included, gets free hosted AI for its first build. When the free usage is spent, Upgrade to Hobby keeps you building, with hosted usage in 5-hour limits; or switch to your own Claude or ChatGPT, which for new accounts needs a plan that includes it. You can also build on your Claude plan (Pro or Max) or your ChatGPT account (any plan, Free included) in the app, your own agent over MCP, or your own API key (OpenAI or Anthropic), and you pay the company that runs your model for it. For new accounts, building on your own AI is free through the first build and on a plan after it: Hobby bought for your own AI, Indie Developer or Studio. The download, the editor, Flockbay's tools, Play and export are free. Generated pictures and sound come with the free hosted AI, and the AI builds 3D models on your computer; only Tripo 3D generation runs on your own Tripo key. Optional plans add hosted AI and your own AI after the first build: Hobby at $49 a month, on Flockbay's AI or your own AI, chosen at checkout and changeable at renewal; Indie Developer at $99, on both, with 2× Hobby's hosted usage; and Studio at $249, on both, with 5×. Hosted usage comes in 5-hour limits inside a monthly limit, on the same Flockbay AI on every plan. Past a limit, on-demand usage keeps building at the plan's rate plus 30%, billed as you go up to a limit you set; on Hobby and Indie Developer it stops before a billing period would cost more than the next plan. Hosted usage makes pictures and sound, and each plan adds the tools to launch a game: Video studio, Social posts, playtest links, Steam page drafting and website publishing, with Ads and more of each from Indie Developer up. Every account makes one free video in Video studio. There is no team, per-seat, or enterprise plan. Projects and assets are private. - **AI models:** The model is yours. On your Claude plan, Flockbay runs Claude Code, and the model menu lists the models and effort levels Claude Code gives you. On your ChatGPT plan, it runs your account's models through the bundled Codex engine. On an API key, it runs any model the key reaches, and an agent over MCP uses whatever model that agent runs. Flockbay's hosted AI, Flockbay in the model menu, is free to start and the same on every plan. - **Your own Claude or ChatGPT plan, in the app.** Pick Claude in the model menu and Flockbay runs Claude Code, Anthropic's coding agent, behind its own chat on your Claude Pro or Max plan; on Windows Claude Code comes with the app, on a Mac it uses the one you installed or installs it with Homebrew, and on Linux it uses the one you installed, and you sign in on Anthropic's page. Or sign in with ChatGPT, on any plan, Free included, and the same chat runs on your ChatGPT account through the bundled Codex engine. A free Claude plan does not build here. - **Your existing Godot project opens.** Flockbay asks once before it adds anything, or opens the project without Flockbay and writes none of its own files. It records what it adds in `.flockbay/added.json`, which git ignores, keeps its editor plugin out of the `project.godot` you commit, and writes nothing permanent to `project.godot` on Play. Play runs what Godot runs, skipping a GDExtension or an autoload Godot would skip, and Uninstall Flockbay from project… takes everything out again. - **Godot versions.** Flockbay works with Godot 4.6+. Godot 4.7.2, standard and .NET, is included, so you do not need Godot installed. Settings › Godot versions lists your own Godot editors found on the computer, and Another version › Locate… adds any other Godot executable; Flockbay does not download a Godot for you. A project last saved by an older Godot 4 offers Keep Godot 4.x, which opens it on your own Godot of that version: on 4.6 that is all of Flockbay, and on an older 4.x Flockbay checks which of its features run and says what is not available; Upgrade to Godot 4.7.2, in place; or Open a copy in Godot 4.7.2. A project from a newer Godot offers Keep or Open a copy. A Godot 3 project offers Keep Godot 3, where the AI edits its files and runs the game without the editor tools or the Game screen, or Convert a copy to Godot 4.7.2, which runs Godot's own converter on a copy and lists what still errors. The project menu's Godot version… changes the engine a project runs on. On a kept engine, Flockbay's MCP class lookups answer from that engine. Detail: [Godot versions and engines](https://flockbay.com/docs/godot-versions-and-engines/). - **Bring your own agent over MCP.** Claude Code, Codex, Cursor or any MCP client can build the game you have open, through one MCP server registered as `flockbay`. In the app, Connectors → Connect your agent (MCP) → Set up → Turn on writes the setup line with your machine's paths filled in. Connecting it is free, with no sign-up; you pay your agent's provider for the model, and new accounts build on it on a plan after the first build. - **Closed source.** The app and Flockbay's instructions are Flockbay's own and not open source. The engine is Godot, under the MIT licence, and the project on your disk is yours. - **Steam:** Flockbay prepares your game's Steam store page (capsules, description, tags, screenshots, price, system requirements) and exports it as a .zip you upload in Steamworks yourself. Preparing the page by hand and the .zip export are free; Steam page drafting by Flockbay is a paid feature, on every plan. Flockbay takes no share of sales. ## Written for AI retrieval - [For AI](https://flockbay.com/for-ai/): structured facts about what Flockbay is, in one place. - [Source status](https://flockbay.com/source-status/): what is Godot's, what is Flockbay's own and closed, and what your project belongs to. - [llms-full.txt](https://flockbay.com/llms-full.txt): every published page with its answer and its questions, in one retrieval instead of a crawl. Asset models, plugin compatibility pages and per-game Steam numbers are listed by their hubs. - [agent-catalog.json](https://flockbay.com/agent-catalog.json): the same map, machine-readable. - [Markdown copies](https://flockbay.com/godot-ai-mcp.md): the landing pages, the docs, the blog (publishing guides and essays) and the Godot 4 answers have their text as Markdown at the same address with .md; this one is /godot-ai-mcp/. ## For developers - [Start here if you use Claude Code, Codex or Cursor](https://flockbay.com/docs/claude-code-codex-and-cursor/): what your agent gets from Flockbay's MCP server, the setup, skills and hooks, and the keys. - [Setup prompt for your agent](https://flockbay.com/docs/agent-setup-prompt/): a prompt that has your agent connect Flockbay and read the project; Markdown at /docs/agent-setup-prompt.md. - [Flockbay plugin](https://github.com/flockbay/flockbay-plugin): the Claude Code plugin, Codex plugin and Gemini CLI extension that register Flockbay's MCP server in one command, on Windows. - [Quickstart: your existing Godot project](https://flockbay.com/docs/quickstart-existing-project/): open it, have the agent explain it, pick one of three small changes, review and revert. - [MCP tool reference](https://flockbay.com/docs/mcp-tool-reference/): every tool the server lists, with its arguments and real example calls. - [Godot AI MCP](https://flockbay.com/godot-ai-mcp/): an agent on a Godot project over MCP, and what Flockbay gives it to call. - [Making games in Claude Code](https://flockbay.com/how-to-make-games-in-claude-code/): connecting Claude Code to Flockbay, with the setup line. - [Making games in Codex](https://flockbay.com/how-to-make-games-in-codex/): connecting Codex to Flockbay, with the setup line. - [Claude Code Game Studios and godogen in Godot](https://flockbay.com/claude-code-game-studios/): running either game-skill repo in a live Godot editor over Flockbay's MCP server, with one real run of each and the tool calls it made. - [Cursor for Godot](https://flockbay.com/cursor-for-godot/): Cursor and Godot, and where Flockbay fits. - [Unity to Godot](https://flockbay.com/unity-to-godot/), [Unity C# to GDScript: the API map](https://flockbay.com/unity-csharp-to-gdscript/) and [Use your Unity Asset Store assets in Godot](https://flockbay.com/unity-asset-store-to-godot/): moving a Unity game to Godot 4, each Unity API with its GDScript checked on Godot 4.7.2, and what Unity's Asset Store licence allows in another engine. - [Import a Unity project](https://flockbay.com/docs/import-from-unity/): Import from Unity makes a new Godot 4 project from a Unity project folder, a .unitypackage or a GitHub repository, without Unity installed; what converts on import, the Port report, and how the AI ports the rest. - [What breaks when a Unity game moves to Godot](https://flockbay.com/blog/what-breaks-when-a-unity-game-moves-to-godot/): two open-source Unity games imported into Godot 4 and one ported to the end; what converted on its own, what the C# needed, and what you still check by playing. - [Connect your own agent](https://flockbay.com/connect-your-own-agent/): what the MCP server exposes and how to set it up. - [Claude for Godot](https://flockbay.com/blog/claude-for-godot/): the ways to connect Claude to a Godot game. - [Best AI tools for Godot](https://flockbay.com/blog/best-ai-tools-for-godot/): the AI tools for Godot, dated, with a verdict on each. - [Flockbay vs Summer Engine](https://flockbay.com/flockbay-vs-summer-engine/): the head-to-head, each fact read from the product's own pages. - [Summer Engine vs Ziva vs Flockbay](https://flockbay.com/summer-engine-vs-ziva/): the three AI tools for Godot side by side, with a verdict on each. - [Ziva alternatives](https://flockbay.com/ziva-alternatives/): the alternatives to Ziva, the AI agent for the Godot editor, dated and sourced. - [Best Godot MCP server](https://flockbay.com/blog/best-godot-mcp-server/): every Godot MCP server with real use, with a verdict on each. - [Best LLM for Godot](https://flockbay.com/blog/best-llm-for-godot/): the best AI for Godot, measured: 28 models on 15 checked Godot 4 coding tasks run headless on the official engine, dated, with game-build head-to-heads. - [AI playtesting](https://flockbay.com/ai-playtesting/): what an AI agent can check by playing a Godot game, and what still needs a person. - [AI devlog maker](https://flockbay.com/ai-devlog-maker/): your own Claude or ChatGPT films your Godot game and renders a narrated 1080p devlog, compared with the other devlog tools. - [Gameplay shorts maker](https://flockbay.com/gameplay-shorts-maker/): vertical TikTok, YouTube Shorts and Reels clips filmed upright from the game, three hooks per moment, with the three real shorts one run made. - [Steam store page kit](https://flockbay.com/steam-store-page-kit/): the Steam page drafted from the game, every capsule and library image cut from a real frame, exported as one .zip for Steamworks. ## Product - [Pricing](https://flockbay.com/pricing/): free to start, AI included. Flockbay's AI or your own Claude or ChatGPT, free for your first build; Hobby, Indie Developer and Studio add more hosted AI, your own AI after it, and the tools to launch a game. - [AI game maker](https://flockbay.com/ai-game-maker/): the category page, and where Flockbay sits in it. - [Godot AI](https://flockbay.com/godot-ai/): how this relates to Godot, for people who already know Godot. - [MCP game development](https://flockbay.com/mcp-game-development/): why a capability layer is a better tool surface for an agent than a pile of engine files. - [Command line](https://flockbay.com/cli/): what exists and what does not. - [No-code game engine](https://flockbay.com/no-code-game-engine/): for people who do not write code, and what "no-code" costs elsewhere. - [Security](https://flockbay.com/security/): where the project lives and what crosses the network. ## Honest answers to common searches - [Browser game maker](https://flockbay.com/browser-game-maker/): it is a download; there is no browser editor. - [Free AI game maker](https://flockbay.com/free-ai-game-maker/): what is free, and whose AI Flockbay runs on. - [Asset store](https://flockbay.com/asset-store/): Flockbay has no marketplace of its own; the four ways art gets into a game. - [VR game maker](https://flockbay.com/vr-game-maker/): it does not target headsets. - [Mobile game maker](https://flockbay.com/mobile-game-maker/): it is a desktop app and does not submit to stores. - [Flockbay vs Unity](https://flockbay.com/flockbay-vs-unity/) and [vs Unreal](https://flockbay.com/flockbay-vs-unreal/): where each one genuinely wins. ## Research - [AI disclosure on Steam](https://flockbay.com/reports/ai-in-games/): what every game released on Steam since 1 July 2023 says in its AI Generated Content Disclosure, classified by which part of the work the AI did. Edition one, 26 August 2026, over a seeded-random sample of the release window. Every rate carries its denominator and its 95% interval; the full text of the report, its tables and its figures are in [llms-full.txt](https://flockbay.com/llms-full.txt). Republishable with attribution. - [Godot LLM Bench](https://github.com/flockbay/godot-llm-bench): fifteen Godot 4 GDScript tasks judged by running them headless on the official engine, with each model's results; MIT. The write-up, with all 28 models measured, is [the best LLM for Godot](https://flockbay.com/blog/best-llm-for-godot/). ## Sections - [Docs](https://flockbay.com/docs/): how the app works, step by step, including connecting your own agent over MCP and building on your Claude plan. - [Publishing an indie game](https://flockbay.com/blog/indie-game-publishing-guide/): the guides to the Steam page, wishlists, Next Fest, demos, trailers, marketing, launch and after, each with sources. - [Blog](https://flockbay.com/blog/): the publishing guides, and game design essays on combat, puzzles, level design, game feel and player psychology. - [Godot 4 answers](https://flockbay.com/godot/): Godot 4 questions answered and checked by running them on Godot 4.7.2. - [Godot plugin compatibility](https://flockbay.com/godot-plugins/): which Godot Asset Library plugins load on Godot 4.7.2, measured. - [Tools](https://flockbay.com/tools/): the Steam and publishing tools (wishlist estimator, wishlist-to-sales and revenue calculators, regional prices, tag lookup, store page checker, short description writer, marketing timeline, devlog titles) and the game name and idea generators. - [Free 3D models](https://flockbay.com/assets/): the CC0 models in the library, by collection and category. - [Guides](https://flockbay.com/guides/): every landing page, grouped by topic. - [Straight answers](https://flockbay.com/guides/answers/): short answers to common questions about Flockbay. ## Optional - [Terms](https://flockbay.com/terms/) - [Privacy](https://flockbay.com/privacy/)