Integration

Capgo integration

Capgo ships live (over-the-air) updates to Capacitor apps. List and manage organizations and their members, register apps, create or reconfigure update channels (stable bundle, platforms, progressive rollout, rollback), register bundles hosted at a public HTTPS URL and assign them to a channel, pin a device to a private channel, and read MAU, storage, bandwidth and bundle-adoption statistics. Assigning a bundle to a channel or changing a channel takes effect on real users' devices at their next update check. API key management is left to the Capgo console, and signed image links, the billing customer id and bundle download links are not returned. Limits: 2,000 requests per minute per key; organization statistics need an active plan. Authentication is a Capgo API key sent in the x-api-key header; each key only reaches the organizations, apps and channels it was granted.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Capgo.Built from the 27 Capgo tools below, on the connection you add once.

What you can do with Capgo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

App, 6 operations

  • create_appCreate appPOSTRegister a new app under an organization. The app_id (reverse-domain) is unique across Capgo and cannot be reused by another account.
  • delete_appDelete appDELETEDelete an app and all its associated Capgo resources. Irreversible; this is not a channel rollback.
  • get_appGet appGETGet one app by its app_id: name, owner organization, default upload channel, last bundle uploaded and retention.
  • get_app_statisticsGet app statisticsGETDaily MAU, storage (bytes) and bandwidth (bytes) for one app over a date range.
  • list_appsList appsGETList the Capacitor apps the API key can read, optionally in one organization. Use it to find the app_id every channel, bundle, device and statistics tool takes.
  • update_appUpdate appPUTUpdate an app's name, icon, retention or block_provider_infra_requests; fields left out keep their value. Does not upload or assign a bundle.

Bundle, 4 operations

  • create_bundleCreate bundlePOSTRegister a bundle zip hosted at a public HTTPS URL (no auth) with its SHA-256 checksum. The version must be valid semver. It goes live only once assigned with set_bundle_channel.
  • delete_bundleDelete bundleDELETEDelete one bundle (version) of an app. Irreversible. Always pass a non-empty version: Capgo reads an empty or missing version as delete EVERY bundle of the app not linked to a channel.
  • list_bundlesList bundlesGETList an app's bundles (versions), 50 per page. With version or id, returns an array of zero or one bundle: use it to check whether a version exists.
  • set_bundle_channelSet bundle channelPUTAssign a bundle to a channel: devices on that channel download it at their next update check. Acts on real users' apps. Ids come from list_bundles and list_channels.

Organization, 4 operations

  • create_organizationCreate organizationPOSTCreate an organization. The key needs the org.create permission (off by default) and an org_admin or org_super_admin binding; Capgo then makes this key super admin of the new organization.
  • delete_organizationDelete organizationDELETEPermanently delete an organization with all its apps, bundles and resources. Irreversible. Needs delete permission on it (typically org_super_admin).
  • list_organizationsList organizationsGETList the organizations the API key can access, 50 per page. Use it to find the orgId that create_app, list_organization_members and the statistics tools take.
  • update_organizationUpdate organizationPUTUpdate an organization's name, management email or logo; fields left out keep their value. Needs the admin role on that organization.

Channel, 3 operations

  • delete_channelDelete channelDELETEDelete a channel of an app; every device on it is affected. With delete_bundle=true the linked bundle is deleted too.
  • list_channelsList channelsGETList the live-update channels of one app (50 per page), with the stable bundle, rollout state and delivery flags of each.
  • upsert_channelUpsert channelPOSTCreate a channel or change one: stable bundle, platforms, auto-update limit, progressive rollout, rollback. Acts on real devices at their next update check. Returns only a status: call list_channels to read the result.

Device, 3 operations

  • list_devicesList devicesGETList the devices of one app with installed bundle, platform and channel override (records are kept 90 days after a device's last activity). Cursor paginated: pass nextCursor as cursor.
  • remove_device_channel_overrideRemove device channel overrideDELETERemove a device's channel override so it follows its normal channel again. The device record is kept.
  • set_device_channel_overrideSet device channel overridePOSTPin one device to a non-public channel so it stops following its default channel. Acts on the real device. The override expires 90 days after this call unless repeated.

Member, 3 operations

  • invite_organization_memberInvite organization memberPOSTInvite an existing Capgo user to an organization, or change a member's role. Acts for real: the user gets an invitation email and the role's access once accepted.
  • list_organization_membersList organization membersGETList the members of one organization with their roles; pending invitations show a role prefixed with invite_. Needs orgId from list_organizations.
  • remove_organization_memberRemove organization memberDELETERemove a member from an organization; their access ends immediately. The last super admin cannot be removed.

Bundle usage, 1 operation

  • get_app_bundle_usageGet app bundle usageGETShare of devices on each bundle (version) of one app per day over a date range, as chart labels and datasets.

Metadata, 1 operation

  • update_bundle_metadataUpdate bundle metadataPOSTSet a bundle's release link or comment without changing its zip. Fields left out keep their value.

Org, 1 operation

  • get_organization_statisticsGet organization statisticsGETDaily MAU, storage and bandwidth across one organization's apps over a date range. Needs an active Capgo plan (402 subscription_required otherwise).

User, 1 operation

  • get_account_statisticsGet account statisticsGETDaily MAU, storage and bandwidth aggregated across every organization the API key can access, over a date range.

Use Capgo from Claude Code, Cursor or Codex

Connect Capgo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Capgo operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Capgo

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Capgo once

    Add your Capgo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Capgo integration FAQ

What can you do with the Capgo integration?

LiveContext exposes 27 operations on Capgo, covering app, bundle, organization and channel.

Popular integrations

Browse the whole catalog