Hosted MCP server

Copy a setup prompt with the install steps and the full markdown guide for this plugin.

Capgo runs a hosted Model Context Protocol (MCP) server so AI assistants can work with your Capgo account: list apps and bundles, move a channel to a new bundle, pause a rollout, check update health, or read native build logs, all from a chat.

https://api.capgo.app/mcp

Nothing to install. Paste the URL into your MCP client.
Streamable HTTP, stateless. It works with any client that supports remote MCP servers.
OAuth 2.1 sign-in. Clients that support MCP authorization open the Capgo console so you can approve access. Clients without OAuth can send a Capgo API key instead.

Connect your client

Clients that support OAuth only need the URL. They discover the Capgo login flow on their own and open the consent page the first time you use the server.

Open Settings → Connectors and choose Add custom connector.
Name it Capgo and paste https://api.capgo.app/mcp as the URL.
Click Connect and sign in to Capgo when the consent page opens.

claude mcp add --transport http capgo https://api.capgo.app/mcp

Then run /mcp inside Claude Code and pick capgo to sign in.

In ChatGPT settings, open Apps & Connectors and turn on Developer mode under the advanced settings.
Create a new connector, name it Capgo, and paste https://api.capgo.app/mcp as the server URL.
Choose OAuth authentication and sign in to Capgo when prompted.

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

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

Cursor shows a Needs login prompt next to the server. Click it to sign in to Capgo.

Add the server to .vscode/mcp.json in your workspace, or run MCP: Add Server from the command palette and choose HTTP:

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

VS Code asks you to sign in to Capgo the first time Copilot Chat uses the server.

Open your Lovable connectors settings and add a custom MCP server.
Paste https://api.capgo.app/mcp as the server URL.
Choose OAuth and sign in to Capgo. If you would rather use a key, choose API key and paste a Capgo API key.

Other clients that implement the MCP authorization spec, such as the MCP Inspector, work the same way: give them the URL and follow the sign-in prompt.

Clients without OAuth (API key)

For n8n, scripts, CI jobs, or any client that cannot run an OAuth flow, send a Capgo API key as a bearer token:

Authorization: Bearer <your Capgo API key>

For example, a client config that accepts custom headers:

{
  "mcpServers": {
    "capgo": {
      "url": "https://api.capgo.app/mcp",
      "headers": {
        "Authorization": "Bearer <your Capgo API key>"
      }
    }
  }
}

Use a key with the smallest role that covers what the assistant needs. See API key permissions.

The hosted server implements OAuth 2.1 with PKCE, following the MCP authorization specification (2025-11-25).

Your MCP client opens the Capgo console consent page (console.capgo.app/oauth/authorize).
You sign in with your Capgo account.
You pick which organizations the client may access.
Capgo creates a dedicated API key named MCP · <client name> for that client.

That key expires after at most 90 days. If an organization enforces a shorter API key expiration policy, the stricter limit wins. After it expires, sign in again from your client to reconnect.

Revoke access

Every connected client has its own MCP · <client name> key. To disconnect a client, delete that key on the API keys page of the Capgo console. The client loses access and has to go through the consent page again to reconnect.

What the assistant can do

The hosted server exposes about 50 tools:

Area	What it covers
Account and organizations	Who am I, organizations, members and invitations, audit logs, API keys
Apps	List, create, update, and delete apps
Bundles	List bundles, update metadata, delete, check usage
Channels and rollouts	Create and update channels, set the bundle on a channel, progressive rollouts (pause, promote, roll back), auto-pause
Devices	List and inspect devices, set or remove channel overrides
Statistics and Observe	App, organization, and account statistics, update health from Observe
Native builds	Build status, build logs, cancel a build
Webhooks	Create, update, test, and delete webhooks, inspect and retry deliveries
Push notifications	Notification settings, providers, campaigns, sending notifications, stats

Each tool calls the Capgo public API with the key from your session. Permissions (RBAC), rate limits, and audit logs behave exactly as they do for REST API calls with that key.

Tools that delete or overwrite data are annotated as destructive, so MCP clients ask you to confirm before running them.

Example prompts

“List my Capgo apps and show the bundle on each production channel.”
“Pause the rollout on the production channel of com.example.app.”
“Why did my last iOS native build fail? Show me the logs.”
“Which devices are still on bundle 1.4.2?”

Hosted vs local MCP

Capgo has two MCP servers. You can use both at the same time.

	Hosted MCP	Local CLI MCP
Endpoint	`https://api.capgo.app/mcp`	`npx @capgo/cli@latest mcp` (stdio)
Install	Nothing, paste the URL	Runs the Capgo CLI on your machine
Auth	OAuth sign-in, or `Authorization: Bearer <API key>`	`npx @capgo/cli@latest login`
Works in	Claude.ai, ChatGPT, Cursor, VS Code, Lovable, n8n, and other remote MCP clients	Desktop and terminal agents that can start local processes
Account management	Apps, bundles, channels, rollouts, devices, stats, Observe, builds, webhooks, notifications	Apps, bundles, channels, organizations, stats
Upload a bundle from your build folder	No	Yes
Request a native build	No (status, logs, and cancel only)	Yes
`doctor`, `probe`, compatibility checks against your project	No	Yes

Use the hosted server for everyday account work from any chat app. Add the local CLI MCP server when the assistant needs your project files.