bitrise-agentic-onboarding

Bitrise Agentic Onboarding (PoC)

A Claude Code plugin marketplace that walks a brand-new Bitrise prospect from "no account" to "shareable public install page" using the agentic-onboarding branch of the Bitrise MCP server.

Status: proof of concept. The signup, code-signing, and provider-OAuth tools the skills depend on live on the agentic-onboarding branch of bitrise-io/bitrise-mcp, which isn't deployed to the hosted MCP endpoint yet. Until it is, the plugin auto-wires the MCP via local go run against that branch.

Quick install

Two commands in your terminal:

claude plugin marketplace add bitrise-io/agentic-onboarding
claude plugin install bitrise-agentic-onboarding@agentic-onboarding

Then start Claude and try:

claude

Onboard me to Bitrise from scratch.

That fires the orchestrator, which runs you through signup → first build → public install page. The first time the MCP runs, go run fetches and compiles the agentic-onboarding branch — expect ~30–90 seconds of silence, then it's fast on every subsequent launch.

What's in the plugin

Four skills:

Skill	Triggers on	What it does
bitrise-signup	"sign me up to Bitrise", "create my Bitrise account"	Anonymous register + verify_registration, installs the returned PAT into the MCP config
bitrise-ci-onboarding	"set up my project on Bitrise", "run my first build"	Register app → repo OAuth → SSH key → stack pick → signing upload → trigger build → watch logs
bitrise-release-management	"share my build", "get a public install link"	Connected app → signed-URL upload → enable public install page → surface URL
bitrise-onboard-end-to-end	"onboard me to Bitrise from scratch", "give me the full demo"	Orchestrator that runs all three with shared state

Plus an mcpServers entry in the plugin manifest that auto-wires the Bitrise MCP from the agentic-onboarding branch via go run.

Requirements

• Claude Code CLI. Cowork desktop's local plugin install isn't supported yet — see the Cowork section below.
• Go ≥ 1.25 on your machine. The MCP is a Go binary that compiles on first launch via go run. Check with go version; install from https://go.dev/dl/ if missing.
• Internet on first run (Go pulls the branch from proxy.golang.org).

How prospects experience it

1. Run the two install commands above. Two minutes, no credentials.
2. Start claude, type "onboard me to Bitrise from scratch".
3. The skill asks for an email; an OTP arrives by mail.
4. The skill installs a fresh Bitrise PAT into the MCP config; restart claude once.
5. Skill asks about the prospect's app — repo URL, platform, optional signing files — then registers it, triggers the first build, watches it go green.
6. Skill enables a Release Management public install page and hands back the URL.

Total time: ~15–30 minutes, dominated by the first build and email/OTP latency. No browser detours required apart from one OAuth step for the git provider.

Cowork desktop

Cowork's local plugin install isn't supported in the current version. This same marketplace will work in Cowork as soon as that ships; until then, prospects use Claude Code CLI as above.

How auth works

• The MCP starts with no BITRISE_TOKEN. That's deliberate — the signup tools (register / verify_registration) run anonymously and need no credential.
• After signup, the orchestrator hands you the new PAT and updates the MCP config. You restart your Claude client once; from then on, every other tool call authenticates via that PAT.
• The PAT is never echoed back into chat. It lives in the MCP client config only.

Why the agentic-onboarding branch

The signup tools, certificate/keystore upload tools, and provider OAuth helpers only exist on that branch. main (and the hosted mcp.bitrise.io endpoint that runs main) would fail on the very first call — register isn't a registered tool there.

Once the branch lands on main and ships to the hosted endpoint, this plugin's mcpServers block in plugin.json can be flipped to:

"mcpServers": {
  "bitrise": {
    "url": "https://mcp.bitrise.io"
  }
}

and skip the local go run entirely.

Known gaps