MCP server for AI-assisted release work
Start the CLI MCP server so agents can list and manage apps, upload bundles, manage channels, check compatibility, request native builds, run diagnostics, and generate encryption keys.
Capgo CLI
Capgo CLI
One terminal for live updates, native builds, compatibility checks, device runs, and AI-assisted Capgo automation through MCP.
MCP
App, bundle, channel, build, stats, and diagnostic tools for AI agents.
Release type
Compatibility checks recommend OTA or native before you ship.
Native builds
Request signed iOS and Android builds and keep output records for CI.
release-terminal
$ npx @capgo/cli@latest bundle releaseType com.acme.app --channel production
Recommendation: OTA update
No native dependency drift detected for production.
$ npx @capgo/cli@latest bundle upload --fail-on-incompatible --qr-preview
Compatibility gate passed. Delta upload ready.
Preview QR generated for device testing.
$ npx @capgo/cli@latest build request com.acme.app --platform ios --output-upload --output-record .capgo/build.json
Build request queued. Output record saved for CI.
What the CLI gives your team
Release automation for CapacitorJS apps with a native safety check built in
The CLI is the path from local Capacitor project to production release. It sets up the app, verifies what can ship OTA, and keeps native build work available when dependencies require it.
Safe live-update uploads
Upload bundles with compatibility gates, delta updates, encryption, metadata, cleanup, and QR preview links for quick test passes.
OTA or native build decision support
Run compatibility or release-type commands before production. When native dependencies change, the CLI points you toward a native build instead of a risky live update.
Native build requests from the same terminal
Request cloud builds for iOS or Android, keep output links and QR records for automation, and avoid parking signing credentials permanently on Capgo.
Device and simulator loops
Initialize the app, run it on physical devices or simulators, and keep the native verification step near the release command.
App, channel, and bundle operations
Use CLI and MCP commands to add apps, update channels, inspect bundles, clean old releases, probe delivery, and read account or organization state.
Command flow
From setup to the right release type
Capgo CLI commands make the important release fork explicit: live update when the web layer changed, native build when the app binary needs to move.
OTA path
Use compatibility gates and preview QR links when the web bundle can move safely.
Native path
Request a signed build when dependencies, permissions, or native code changed.
- 1
Initialize updates, upload, build, and verification flows
npx @capgo/cli@latest init - 2
Ask whether a release should be OTA or native
npx @capgo/cli@latest bundle releaseType com.acme.app --channel production - 3
Upload a guarded live update with a preview QR
npx @capgo/cli@latest bundle upload --channel production --fail-on-incompatible --qr-preview - 4
Request a native build and keep output for CI or PRs
npx @capgo/cli@latest build request com.acme.app --platform ios --build-mode release --output-upload --output-record .capgo/build.json - 5
Expose Capgo tools to an MCP-compatible agent
npx @capgo/cli@latest mcp
Native builds and MCP
Let the CLI handle the release work your app actually needs
When compatibility says the change is OTA-safe, ship a guarded live update. When native code, permissions, or dependencies changed, request a native build and keep the output visible for CI, PRs, and reviewers.
Apps
Bundles
Channels
Compatibility
Native builds
Stats
Doctor
Delivery probe
Build record
iOS release build
Saved output for CI, PR checks, and mobile review.
- Platform
- iOS
- Mode
- release
- Output
- IPA and install QR
- Record
- .capgo/build.json
npx @capgo/cli@latest build request com.acme.app --platform ios --output-upload --output-record .capgo/build.json Status is visible before release notes are posted.
QR output stays available for device validation.
Errors can fail CI before a risky release ships.
Apps built with Capacitor
Capacitor apps need release tooling that respects native boundaries
Large Capacitor apps mix web changes with native dependencies. The Capgo CLI keeps that boundary visible before a production release goes out.
Apps shown are sourced from a public store app dataset used across the website.
WEATHER
Windy.com - Weather Forecast
32.9M installs 4.7 rating
View store listing
TOOLS
Mi Orange
9.3M installs 4.2 rating
View store listing
TOOLS
My Vodafone
11.1M installs 4.6 rating
View store listing
CLI proof
Release workflows people trust from terminal to production
Short reviews from teams using Capgo for Capacitor updates, native builds, and release control.
Nate van Jole
CTO, Private
“Getting set up took less than a day. Channel-based rollouts let me test on my own device before anything hits production users.”
no-tone @ Webincode
Developer, Webincode
“Being able to add Device ID's to certain groups and push the changes to only certain groups is a life saver.”
sikafanka
Design, radius 5
“Capgo Build helped us simplify our Capacitor app release process. We can build and ship iOS and Android apps from one clear workflow.”
Use the CLI today
Add Capgo to your release scripts without waiting on a dashboard session.
Start with the CLI docs, then wire compatibility checks, bundle uploads, native builds, or MCP into the workflow your team already uses.