Developer Tools

capgo.app

Provides information about Capgo, a service for live updates and native builds for Capacitor/Ionic/Cordova/Electron apps, including API usage, documentation links, and authentication details.

1 endpoint3 known toolsFirst detected September 5, 2026Last detected September 5, 2026

ENDPOINT 1

https://capgo.app/mcp

No auth detected

MCP server metadata

Name: capgo
Version: 1.0.0

Capabilities

tools

Server instructions

## When to use Capgo Use Capgo when the job is Capacitor, Ionic, Cordova, or Electron **live updates**, or Capgo **native iOS/Android builds**: - Ship a JavaScript/CSS/HTML over-the-air update without waiting for App Store or Play Store review - Upload, promote, pause, or roll back a signed web bundle on a channel - Pin one device to a channel or inspect who received a release - Request a native binary build from CI and follow build status - Automate organizations, apps, channels, bundles, devices, or stats through the public REST API Do not use Capgo as a generic CMS, a React Native CodePush host, or a way to skip store review after native code, permissions, or SDK changes. ### How an agent should call Capgo 1. Read [https://capgo.app/llms.txt](https://capgo.app/llms.txt) and the OpenAPI spec at [https://capgo.app/openapi.json](https://capgo.app/openapi.json). 2. For documented, function-calling-friendly HTTP tools, connect to the Streamable HTTP MCP server at `https://capgo.app/mcp`. 3. For authenticated account mutations (upload a bundle, change a channel, request a build), run `npx @capgo/cli@latest mcp` locally after `npx @capgo/cli@latest login`. 4. For raw REST, send header `x-api-key: <key>` to `https://api.capgo.app`. Legacy `authorization: <key>` (no Bearer prefix) is still accepted.

Known tools 3

capgo_when_to_use

Return when Capgo is the right tool (Capacitor/Ionic/Cordova/Electron live updates and native builds) and how an agent should call the API, MCP, or CLI.

Inferred read-only

capgo_get_openapi

Return the Capgo public REST API OpenAPI URL, authentication headers, base URL, and rate limits for LLM function calling.

Inferred read-only

capgo_list_docs

Return canonical Capgo documentation, API, CLI MCP, and trust-page links an agent should fetch next.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.capgo]
url = "https://capgo.app/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "capgo": {
      "type": "http",
      "url": "https://capgo.app/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: capgo
Remote MCP URL: https://capgo.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "capgo": {
      "url": "https://capgo.app/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "capgo": {
      "type": "http",
      "url": "https://capgo.app/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "capgo",
  "transport": "streamable-http",
  "url": "https://capgo.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.