BuildBakeryRequest access

AI coding agents

Agents can set up recipes, start batches, read logs and failure analyses, and retry. Give your agent two things:

  • The skill (or instructions file): teaches it how to use BuildBakery: recipes, signing, checking deliveries before anything is published, and when to fall back to the CLI.
  • The MCP connection: gives it the ability to act: start and cancel batches, read logs, see simulator screenshots, re-send deliveries. Without it, the agent uses the bakery CLI instead.
MCP tools · https://buildbakery.com/api/mcp
list_projects     list_batches      start_batch       get_batch
get_job_log       explain_failure   cancel_batch      validate_recipe
list_ovens        list_deliveries   deliver_batch     update_delivery
test_delivery     list_accounts     test_account      list_ingredients
get_screenshots

Claude.ai and the Claude apps (web, desktop, phone)

1. Add the skill

  1. Download buildbakery-skill.zip.
  2. In Claude.ai, open Settings → Capabilities → Skills, choose Upload skill and pick the zip. Re-upload it when BuildBakery adds features (the file stays at the same address).

2. Add the connector

  1. Open Settings → Connectors → Add custom connector, name it BuildBakery, and enter the URL https://buildbakery.com/api/mcp. No token needed.
  2. Click Connect, sign in to BuildBakery and Allow, for all your projects or just one. It shows up on Account → API tokens as a connector, where you can revoke it.
  3. Both now work in Claude on the web, desktop and phone. Turn the connector on in a chat from the tools menu if it isn't already.

Coding agents (Claude Code, Codex, Cursor and others)

The same two pieces, per agent. Pick yours:

Claude

Anthropic · Agent Skill for Claude Code, the Claude apps and the Claude API

1. Add the instructions to the repository

Commit the files so teammates' agents and cloud agents get them too.

curl -fsSL https://buildbakery.com/install-cli.sh | sh
bakery ai install --tool claude

For every project on this machine instead: bakery ai install --tool claude --global

Writes .claude/skills/buildbakery/SKILL.md. To install by hand, save the file at that path.

Claude.ai, desktop and mobile apps: Settings → Connectors → Add custom connector, URL https://buildbakery.com/api/mcp, then Connect, sign in to BuildBakery and Allow (all projects or one). Upload buildbakery-skill.zip under Settings → Capabilities → Skills so Claude also knows how to use it. Headless or CI instead of a browser sign-in: add --header "Authorization: Bearer $BAKERY_TOKEN" to the claude mcp add command.

2. Connect the MCP server

Agents use the MCP tools when connected and fall back to the CLI. Agents that support it sign in through your browser and you approve them (all projects or one); otherwise use an API token from Account → API tokens. MCP setup for Claude (Claude Code, all projects; then /mcp → buildbakery → Authenticate):

claude mcp add --scope user --transport http buildbakery https://buildbakery.com/api/mcp
claude mcp list   # buildbakery should show as connected after /mcp → Authenticate

Example requests

Set this repo up on BuildBakery and bake the Android and iOS builds.
Batch 12 burnt. Find out why, fix it and bake again.
Ship the iOS build to TestFlight and tell me which build number it got.
Move our builds off GitHub Actions to BuildBakery.
Add a signing check so a debug-signed APK can never be delivered.

With pull request builds turned on, each change an agent pushes gets a PR comment with an install link, which works when you're driving the agent from a phone.

Request accessRecipe reference