Skip to content

AI and agents

Connect your agent (MCP)

The Flockbay app runs an MCP server for the game you have open. Turn it on in Connectors, copy the setup line for your agent, and Claude Code, Codex, Cursor or any other MCP client builds in that game with Flockbay’s tools.

What it is

MCP is the Model Context Protocol, the open standard agents use to call tools. The Flockbay app serves one MCP server over stdio. It hands your agent the tools to work in the game you have open: scenes, nodes, scripts and resources through the Godot editor, Play and the running game, the asset library, 3D models, version control and plugins. The MCP tool reference lists every tool.

The app writes the setup for Claude Code, Cursor, Codex, Gemini CLI, Cline, Kilo Code, OpenCode, Goose, Devin Desktop and LM Studio, and a local model through Ollama by way of one of those. Any other MCP client that can start a local stdio server works with the same command.

This is the reverse of building on your Claude or ChatGPT inside the app. There, your plan runs Flockbay’s own chat. Here, your agent stays where it is and reaches into your project.

Turning it on

  1. Open the Flockbay app with a game. The connection needs a Flockbay account, and the app makes a free one on first launch.
  2. Open Connectors and press Set up on the Connect your agent (MCP) row. The project menu at the top of the chat has Connect your agent (MCP)… too.
  3. Press Turn on. The dialog shows "MCP server … · On · serving" and your game’s name.
  4. Choose your agent under Your agent. The dialog shows its whole setup line or config block: read it, press Copy, and put it where the line under it says.
  5. Start a new session in your agent. Flockbay’s tools are listed in it.

On Windows the line runs flockbay mcp, the command the installer puts on your PATH, so it is the same on every machine and keeps working after updates. On a Mac or Linux the line holds the paths to this installation, so copy it from the dialog, not from a web page. You add it once; the app keeps the connection on for whichever game you open next until you press Turn off.

The setup line

On Windows, after installing Flockbay, run this in a new terminal for Claude Code or Codex, or press the button for Cursor or VS Code. On a Mac or Linux, copy the line from the dialog instead. Then turn the connection on in the app, as above.

PowerShell
claude mcp add --scope user flockbay -- flockbay mcp
codex mcp add flockbay -- flockbay mcp

Where each agent’s setup goes

Claude Code and Codex: a command. Paste it in a terminal. It registers the server for your user, so every folder you start the agent in has it.

Cursor: a JSON block for ~/.cursor/mcp.json (on Windows, %USERPROFILE%\.cursor\mcp.json), or press Add to Cursor. Gemini CLI: ~/.gemini/settings.json. Cline: MCP Servers, then Configure, then Configure MCP Servers, and add it to that file. Devin Desktop: ~/.codeium/windsurf/mcp_config.json (on Windows, %USERPROFILE%\.codeium\windsurf\mcp_config.json). LM Studio: Program, then Install, then Edit mcp.json, or press Add to LM Studio.

Kilo Code: ~/.config/kilo/kilo.jsonc, or kilo.jsonc in your project folder. OpenCode: opencode.json in your project folder, or ~/.config/opencode/opencode.json. Goose: a YAML block for ~/.config/goose/config.yaml.

Ollama runs the model, not the agent. Run your Ollama model in Goose, OpenCode or Cline, and use that agent’s setup.

Checking the connection

In Claude Code, the server shows under /mcp inside a session, and in a terminal with claude mcp list. In Codex, codex mcp list lists it. Both say whether it connected.

Terminal
claude mcp list
codex mcp list

Skills and hooks

Under the setup line, the dialog offers Flockbay’s skills for the agents that read skills, and says what pressing it writes before you press it.

For Claude Code, Install skills and hooks copies Flockbay’s skills to ~/.claude/skills and adds 3 hooks (SessionStart, PostToolUse, Stop) to ~/.claude/settings.json. For Cursor it copies the skills to ~/.cursor/skills and adds 2 hooks (sessionStart, stop) to ~/.cursor/hooks.json. The hooks run in every session of that agent on this computer and do nothing outside the game Flockbay serves.

For Codex and Goose, Install skills copies Flockbay’s skills to ~/.agents/skills.

Remove skills and hooks (Remove skills for Codex and Goose) takes out what Flockbay installed, and says how many skills and hooks it removed. Your own skills and hooks stay. If your agent’s settings file is not valid JSON, Flockbay changes nothing in it and says so.

What your agent can reach

A connected agent gets Flockbay’s tools for the game you have open. Those tools edit and delete the game’s files and run scripts in the game, the Godot editor and Blender on this computer, without asking, whatever your agent’s own sandbox or permission mode allows.

The tools that change scenes, scripts, resources and signals work through the Godot editor, so they need the game open there; the tools that look into the running game need it running. Work your agent does shows in its own chat in the app, named "Your agent", one step per tool call.

Three rules while your agent works

Flockbay never starts the game under you. If you are playing, the game does not restart: the chat offers you Play instead, and your agent is told why. While Flockbay’s own AI has a turn running in the game, your agent is asked to wait until it ends. Pictures of the game and of the editor never move your screen, and a headless run never opens a window.

Your hands win. If you press a key, click or press a gamepad button while your agent is playing input into the game, its input stops at once, everything it was holding is let go, and it is told you took over. A paused game, because you are on another screen or in the Esc menu, gets no input from it at all.

Every editor change is one Ctrl⌘+Z. Each change your agent makes through the editor is one step in Godot’s undo history, named for what it did, such as "Flockbay: Add Player", and the scene is saved after it. A new scene or resource file stays on disk when its step is undone, and project settings and input actions are written by the app, not the editor, so Ctrl⌘+Z does not take them back.

If it does not connect

Your agent lists only flockbay_status: the app is not serving it yet. The app has to be open with a game, and Connect your agent (MCP) on. Flockbay’s tools are added to the same connection by themselves once it is; if they do not appear, start a new session in your agent.

The dialog says "The connection couldn’t start on this computer:" in red, with the reason: the app ran the setup line itself and the server did not start. The line stays in the dialog so you can see what failed. Press Turn off, then Turn on, and start a new session in your agent.

Your agent shows the server as failed, or Flockbay’s tools are gone after the app updated: copy the setup line from the dialog again and paste it, and remove the failed entry with your agent’s own command, such as claude mcp remove or codex mcp remove with the name mcp list shows.

"Flockbay’s skills have not downloaded yet": turn Connect your agent (MCP) off and back on, then press Install again.

Still stuck: Troubleshooting says how to send logs and where to ask.

What it costs

Nothing. Your agent runs on your machine with your own model and subscription, so its tokens are paid to whoever provides that model. A few tools make assets on Flockbay’s keys, such as a concept sheet or a sound effect, and count against your hosted usage like a turn in Flockbay’s chat; the 3D model tool runs only on your own Tripo key.

From a command line

The app takes three flags, for an agent or a script that wants a game without anyone at the window: flockbay-desktop.exe --open-game <folder> --your-own-agent on on Windows, and the same flags on the Mac app and the Linux AppImage. --open-game opens the game in that folder in the editor, and makes a new one there when the folder is empty or missing (add --2d for a 2D game); a Godot project already there is added to Flockbay. --your-own-agent on turns the connection on for that game, as Turn on does, and the command prints the same setup line the dialog shows. With the app already running, the command hands both to it. No link can do this: it works only from a command line on your own machine.

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

See also: MCP game development.