The official MCP server for Capawesome, the platform Capacitor teams use to build, update and publish their apps. Without a token it gives Claude the current Capawesome documentation — the Capacitor plugins, Capawesome Cloud, Capawesome Insiders and the CLI — through three read-only tools: search the documentation, read a full page, and list recent blog posts. That alone stops Claude answering plugin questions from stale training data. With a Capawesome Cloud API token it also opens the Capawesome Cloud management API: 82 further tools across 16 toolsets covering apps, live update channels and deployments, native iOS and Android builds, signing certificates, build environments and secrets, app store destinations, devices, Git connections, jobs, license keys, organizations and teams. Trigger a native build, ship a live update, roll back a channel or diagnose a failed job without leaving the conversation. Every tool carries MCP annotations marking it read-only or destructive, so Claude asks for confirmation before anything that writes. Add ?readonly=true to the server URL to register only the tools that cannot write or delete, and ?toolsets= to register a smaller, sharper set. The token acts on behalf of the account that created it, through the same Capawesome Cloud API as the CLI — the same permissions, network restrictions and rate limits apply. It is never stored by the server. No tool deletes an app or an organization, and there are no bulk deletes. Create an API token in the Capawesome Cloud Console at https://console.cloud.capawesome.io/settings/tokens
