Broctic

The Broctic MCP server

Connect Claude Code, Codex, Cursor or any MCP client to Broctic: build and ship apps, read your numbers, and give the agent the reference it needs.

What it is for

Most apps are instrumented and optimised by a coding agent now. That agent can read your repository, but it cannot see what Apple reported yesterday, where people are actually stopping, or which of your numbers is already beating its published band. The MCP server gives it both halves — and, just as importantly, the reference it needs to not make things up.

An agent with the tools and no reference invents event names, which are stored faithfully and compared to nothing, and invents conversion statistics, which are worse than no statistics because they sound like measurements. So the whole reference travels with the server: the vocabulary, both client files, and every figure with its source.

Connect it

One file is the server and its installer. It needs Node 22 or later.

terminal
mkdir -p ~/.broctic
curl -fsSL https://broctic.com/downloads/broctic.mjs -o ~/.broctic/broctic.mjs
node ~/.broctic/broctic.mjs login     # paste an organization key (brk_…); stored once in ~/.broctic
node ~/.broctic/broctic.mjs install   # Claude Code, Codex and Cursor, for every project

install registers the server at user scope in Claude Code, in Codex (~/.codex/config.toml) and in Cursor (~/.cursor/mcp.json), and adds a short skill that tells a new session Broctic exists — so it works in any folder, not only inside one project. No key is written into any of those files; the server reads it from ~/.broctic/credentials.json (readable only by you), so rotating it is one login. node ~/.broctic/broctic.mjs status shows what is set up.

Any other MCP client

mcp.json
{
  "mcpServers": {
    "broctic": {
      "command": "node",
      "args": ["/Users/you/.broctic/broctic.mjs"]
    }
  }
}

Toolsets

By default the server offers the Studio tools — build, edit, run, capture, audit, ship — about two dozen of them. The App Store, screenshot, analytics, monetization and research tools are separate toolsets, because every tool is context your agent pays for on every turn and some clients stop at around forty. Add them with install --toolsets studio,store, or set BROCTIC_TOOLSETS=all.

The key is an organization API key (prefix brk_) from Settings → API keys — it reads and changes your account, so it stays on your machine and never goes in an app. The publishable key an app ships with (bpk_) is a different thing and will not work here. BROCTIC_TOKEN in the environment overrides the stored key. Resources and prompts work without any key.

What it will not do

  • Invent a statistic. Every figure it can quote is attributed, and the prompts say so repeatedly.
  • Quote a percentage from a funnel with too few people. Under fifty, the report withholds rates on purpose and returns counts.
  • Interpret your numbers for you. The verdicts come from the API with their citations attached; the server does not add a second opinion nobody can audit.

The source is in the platform repository under packages/mcp.