By bitrise-io
Walks a Bitrise prospect from no account to a public install page using the agentic-onboarding branch of the Bitrise MCP. Includes one skill per stage (signup, CI first build, Release Management) and an orchestrator that runs all three.
Take a Bitrise prospect from "I have an account" to "my first build is green" by registering a project, connecting a repo, uploading signing credentials, and triggering the first build via the Bitrise MCP server. Use this when the user asks to "set up my project on Bitrise", "connect my repo to Bitrise", "run my first Bitrise build", "onboard my app to Bitrise CI", or "get my iOS/Android app building on Bitrise". The user must already have a Bitrise PAT wired into the MCP — if they don't, run bitrise-signup first. Use this skill regardless of whether it's iOS or Android; the skill branches internally.
Run the full Bitrise prospect onboarding journey end-to-end in a single session: sign up for a Bitrise account, register an app and run a first CI build, then publish a public install page via Release Management. Use this whenever the user expresses intent for a complete Bitrise evaluation — e.g., "onboard me to Bitrise", "I want to try Bitrise from scratch", "set me up on Bitrise end to end", "walk me through Bitrise", "give me the full Bitrise demo", "I want to go from zero to a shareable install link". Prefer this skill over the individual stage skills when the user signals they want the whole journey, not just one piece.
Take a Bitrise prospect from "I have a working CI build" to "I have a shareable public install page link" by registering the app in Bitrise Release Management, uploading the installable artifact (IPA / APK / AAB), enabling the public install page, and surfacing the URL. Use this when the user asks to "share my build", "get an install link", "send a build to testers", "set up Release Management", "publish a beta", or "get a public install page". The user must already have a Bitrise account, an app registered in Bitrise CI, and at least one successful build with a distributable artifact. If they don't, route them to bitrise-signup or bitrise-ci-onboarding first.
Sign a brand-new prospect up to Bitrise from inside Claude using the Bitrise MCP server's anonymous registration tools. Use this whenever the user says things like "sign me up to Bitrise", "create my Bitrise account", "I want to try Bitrise", "start a Bitrise trial", or expresses interest in trying Bitrise but doesn't have an account yet. Also use as the first step when the user asks for end-to-end Bitrise onboarding. Do NOT use this skill if the user already has a Bitrise PAT configured — go straight to bitrise-ci-onboarding.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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-onboardingbranch 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 localgo runagainst that branch.
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.
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.
go run. Check with go version; install from
https://go.dev/dl/ if missing.proxy.golang.org).claude, type "onboard me to Bitrise from scratch".claude once.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'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.
BITRISE_TOKEN. That's deliberate — the signup
tools (register / verify_registration) run anonymously and need no
credential.agentic-onboarding branchThe 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.
npx claudepluginhub bitrise-io/agentic-onboarding --plugin bitrise-agentic-onboardingPermanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Production-grade vibe coding suite. Structured workflows from discovery to deployment: start, build, ship, fix, refactor.
Semantic search for Claude Code conversations. Remember past discussions, decisions, and patterns.
Memory compression system for Claude Code - persist context across sessions
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.