Capgo Hosted MCP Server

Connect an assistant to Capgo account operations for apps, channels, rollouts, devices, update health and native build logs.

Remote serverstreamable-http

What is the Capgo Hosted MCP Server?

Capgo’s hosted MCP server connects an assistant to the account behind a Capacitor app. It can inspect apps and bundles, manage channels and rollouts, look up devices, and retrieve update health or native build logs.

Connect your account

Add https://api.capgo.app/mcp to a client that supports remote MCP servers. The connection uses Streamable HTTP. OAuth-capable clients open Capgo’s sign-in and consent flow; clients without OAuth can send a Capgo API key as a bearer token. Choose the organizations the assistant needs to access.

A useful release workflow

Begin by checking which bundle a channel serves. Inspect update health or affected devices before deciding whether to pause, promote or roll back a rollout. For a failed native build, retrieve its status and logs to understand the failure.

When to use the local server

The hosted connection cannot read a build folder on your computer. Uploading a local bundle, requesting a native build, and running project diagnostics belong to the separate Capgo CLI MCP server.

Account permissions and API limits still apply to tool calls. Inspect the target app and channel before confirming a change.

Capgo hosted MCP documentation.

How to install the Capgo Hosted MCP Server

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

The documented Cursor-style configuration. Sign in through the client’s OAuth prompt.

Configuration

A Capgo account and a client that supports remote Streamable HTTP MCP connections.