Capgo
app.capgov1.0.0Updated Oct 8, 2026
Ship and update Capacitor apps: live updates, channels, rollouts, devices, native builds, stats.
Overview
AI-generated overview
Lets an assistant manage Capacitor app releases, live updates, channels, rollouts, devices, native builds, and stats through Capgo.
- What it does
- Capgo exposes its app delivery platform to an assistant over a remote MCP endpoint. Based on the description, it covers shipping and updating Capacitor apps: live updates, update channels, staged rollouts, device records, native builds, and usage statistics. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Worth adding when a team already uses Capgo for Capacitor app delivery and wants an assistant to inspect or act on releases, channels, rollouts, devices, builds, or stats without leaving the chat. Less useful if you do not ship Capacitor apps or do not use Capgo.
- Requirements
- A remote streamable HTTP endpoint at The manifest declares no authentication, environment variables, or headers, but a Capgo account and API credentials are likely needed in practice; confirm with the provider.
Before you install
The manifest declares no authentication, which is unusual for a service that can ship app updates; verify how access is actually secured before connecting. Operations around live updates, channels, rollouts, and native builds can change what users receive, so review any write or release action before approving it.
Installation
In SourceWeft
- Open Capgo in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"capgo": {
"type": "http",
"url": "https://api.capgo.app/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 8, 2026


