Capgo Cli Usage

Capgo CLI Usage

Use this skill as the entry point for Capgo CLI command routing.

When to Use This Skill

• User asks generally how to use the Capgo CLI
• The request spans multiple Capgo command groups
• The right Capgo sub-workflow is not obvious yet

Routing

Route specific workflows to the matching skill:

• OTA bundles and channels -> capgo-release-management
• native cloud builds -> capgo-native-builds
• organizations and account commands -> capgo-organization-management

Connect the Agent to Capgo (MCP)

Capgo has two MCP servers. Use both when available.

• Hosted MCP: https://api.capgo.app/mcp (streamable HTTP). Nothing to install; the client signs in with OAuth, or sends Authorization: Bearer <Capgo API key>. The hosted MCP includes destructive tools, so use an API key with the smallest role the task needs (read-only for reporting). Covers apps, bundles, channels, progressive rollouts, devices, stats, update health, native build status and logs, webhooks, and push notifications. Example for Claude Code: claude mcp add --transport http capgo https://api.capgo.app/mcp, then /mcp to sign in.
• Local CLI MCP: npx @capgo/cli@latest mcp (stdio). Needed to upload a bundle from the build folder, request a native build, or run doctor.

No Capgo account yet: sign up at https://console.capgo.app (14-day free trial, no credit card). Docs: https://capgo.app/docs/ai/mcp/

Common Commands

• init
• login
• doctor
• probe
• app add
• app list
• app delete
• app set
• app debug
• mcp

Prefer the current CLI form:

npx @capgo/cli@latest doctor

Error Handling

• If the request is specific enough for a narrower Capgo skill, switch to that skill instead of staying at the routing layer.
• For CLI auth issues, fix login first before troubleshooting downstream commands.