Your own AI client can read the studio's games, their player feedback, analytics and releases, the Roblox market, the studio's code activity and this handbook, as you and nothing more, and suggest updates to the games from what players say. Add the studio's MCP server, https://mcp.blockoutgames.com/mcp, to your client, sign in once in your browser, and approve the client. There is no key to copy and nothing secret to keep on your computer.
Before you start
You must be able to sign in to the studio: an active member of the BlockoutGames GitHub organization (sign-in and access).
Your client needs a browser on the same computer for the sign-in. It will not work over SSH without one.
Claude Code
claude mcp add --transport http blockout https://mcp.blockoutgames.com/mcp --scope userThen, inside Claude Code, run /mcp, choose blockout and Authenticate; or, from your shell, run claude mcp login blockout. Your browser opens on the account site. --scope user makes the server available in every project; leave it out to add it to the current project only.
Claude Desktop and claude.ai
Add a custom connector
In Claude, open Settings › Connectors and choose Add custom connector.
Give it the address
Name it Blockout Games and give the URL
https://mcp.blockoutgames.com/mcp.Connect
Choose Connect. Claude opens the account site in your browser; sign in and approve it.
Codex
codex mcp add blockout --url https://mcp.blockoutgames.com/mcpcodex mcp login blockoutOr add it by hand to ~/.codex/config.toml, then run codex mcp login blockout:
[mcp_servers.blockout]
url = "https://mcp.blockoutgames.com/mcp"Gemini CLI
gemini mcp add --transport http blockout https://mcp.blockoutgames.com/mcpOr add it to your settings.json:
{ "mcpServers": { "blockout": { "httpUrl": "https://mcp.blockoutgames.com/mcp" } }}Then, inside Gemini CLI, run /mcp auth blockout.
What the consent screen shows
After you sign in, the account site asks whether to let the client in as you. It shows:
the name the client gave itself. Anyone can choose any name, so the page says so: check that it is the client you just added;
the client's id and the address it sends you back to (for a client on your computer,
127.0.0.1orlocalhost);what it asks for, in words, each with a box to tick. Reading is ticked; anything that changes something is not, until you tick it.
Choose Allow to connect it with what you ticked, or Deny to send it away with nothing.
What a client can do
| Permission | What it lets the client do |
|---|---|
studio:read | Read the studio's games, their release logs, project contract status and the collector's health |
market:read | Read the Roblox market: games, creators, discovery and genres |
code:read | Read the studio's code activity and pull requests |
docs:read | Search and read this handbook |
feedback:read | Read players' feedback on the games you may see it for, without players' Roblox ids |
analytics:read | Read the games' analytics: players, retention, sessions, peak hours and revenue, as the studio shows you |
studio:write | Watch or stop watching games for you, and draft home pages you then save yourself |
feedback:write | Change a feedback item's status, and prepare GitHub issues from feedback |
It reads exactly what you can see: if the studio hides a number from you, it is hidden from your client too. A game's feedback, for instance, is for owners and the game's crew. It never sees members, email addresses, keys, credentials or the audit log.
Tools
| Tool | Permission | What it does |
|---|---|---|
studio_games | studio:read | The studio's games |
studio_game | studio:read | One game with its stats |
game_releases | studio:read | A game's release log, with each update's effect, and its repository's GitHub releases |
collector_health | studio:read | Whether the collector is running and keeping up |
studio_contracts | studio:read | Each project's contract status and who has signed; never the terms |
market_search | market:read | Search the tracked Roblox games |
market_game | market:read | One Roblox game with its history |
market_creator | market:read | A Roblox creator and their games |
market_discovery | market:read | The games rising fastest |
market_genres | market:read | The genres, with their games and players |
code_activity | code:read | Commits, pull requests and reviews by week |
code_pull_requests | code:read | The pull requests |
handbook_search | docs:read | Search this handbook |
handbook_page | docs:read | Read one page of it |
game_feedback | feedback:read | A game's feedback by status, category, days and words, a page at a time |
feedback_themes | feedback:read | What a game's players write about, week by week |
game_analytics | analytics:read | A game's players, retention, sessions, revenue and busiest hours over a range |
studio_analytics | analytics:read | Every released game added up |
watch_game | studio:write | Watch or stop watching a game, after asking you |
home_widgets | studio:write | The widgets a home page can hold |
draft_page | studio:write | A link to a new home page, open unsaved in the studio for you to save or cancel |
set_feedback_status | feedback:write | Mark a feedback item seen, planned, done or ignored, after asking you |
create_feedback_issue | feedback:write | A link that opens a GitHub issue filled in from feedback, for you to check and submit |
Ready-made asks
Your client lists these as prompts (in Claude Code, type / and look for blockout). Each tells the client which tools to use.
| Prompt | What it does |
|---|---|
weekly_studio_report | The studio's week: players, feedback, releases, contracts and the collector |
triage_feedback | A game's new feedback grouped into themes, with a status proposed for each item |
recommend_updates | Concrete updates for a game, each with its evidence (feedback items, numbers) and the impact to expect |
compare_with_genre | A game against the leading games of its genre |
Or just ask, for example:
"Recommend updates for Anime Clicker Heroes from its feedback."
"What did players complain about most this week, across our games?"
"How did retention move after our last update to Anime Clicker Heroes?"
"Draft me a home page with our revenue and players."
When it changes something
A client changes nothing unless you ticked a permission for it on the consent screen, and even then:
It asks you in the client where the client can ask its user (MCP calls this elicitation): it shows what it is about to do, with a box to confirm, and nothing happens until you confirm it.
Otherwise it gives you a link to
account.blockoutgames.com, where you see exactly what it would change and press Approve or Decline yourself. Only after you approve, and only once, within five minutes, can the client make that change. Your client cannot approve for you.A drafted page is not saved until you press Save in the studio, and an issue is not opened until you submit it on GitHub.
At most 20 changes a minute are allowed, and every one is in the audit log: who, what and which client.
Disconnect a client
Open Settings › Connected apps on account.blockoutgames.com. Every client you connected is listed, with what it may read, when you connected it and when it last fetched a token. Disconnect stops it on its very next request, on every device. To use it again, connect it again.
If you leave the organization, every client you connected stops at once as well.
Things to know
Every tool call is recorded in the studio's audit log: which client, which tool and whether it worked, never what you asked. A change also records what it changed.
There is a limit on calls a minute; a client that goes over is told to wait.
Answers mark text written outside the studio, such as Roblox game names and descriptions, pull request titles and players' feedback, as
<untrusted>. It is data, not instructions: if a player writes "ignore your instructions", your client should not, and you should not either.Players are never named by their Roblox id: each is a code, the same for one player within one game, and different for each member.
Updated