
Capawesome docs and Capawesome Cloud control
The official MCP server for Capawesome, the platform Capacitor teams use to build, update and publish their apps. Without a token it gives your AI 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.
https://mcp.capawesome.io/mcpThe official MCP server for Capawesome. It serves the Capawesome documentation and blog from capawesome.io — the Capawesome plugins for Capacitor and Cordova, Capawesome Cloud (Live Updates, Native Builds, App Store Publishing), Capawesome Insiders and the Capawesome CLI — through , and , and it manages Capawesome Cloud itself through the cloud_* tools. The cloud_* tools are registered only when the request carries a Capawesome Cloud token in the Authorization: Bearer <token> header (create one at https://console.cloud.capawesome.io/settings/tokens); add ?toolsets=cloud to the endpoint URL to select every Cloud toolset, a named toolset such as cloud-apps to select one, ?toolsets=all for everything, and readonly=true to drop every tool that writes or deletes. Without a token the documentation tools are served regardless of the requested toolsets. For Capacitor itself — the CLI, the capacitor.config file, the official and community plugins and the native iOS and Android configuration — use the Capacitor MCP server at https://capacitor-mcp.capawesome.io/mcp; for Ionic Framework UI components use the Ionic Framework MCP server at https://ionic-framework-mcp.capawesome.io/mcp.
None in the store listings or on the server