Agent skill · capawesome-team
capawesome-mcp
Guides the agent through connecting an MCP client to the hosted Capawesome MCP server, which exposes always-current Capawesome documentation search and the Capawesome Cloud management API. Covers setup for Claude Code, Claude Desktop, Cursor, and VS Code, API token creation, toolset selection, read-only mode, secret handling, verification, and troubleshooting. Do not use for installing Capacitor plugins, migrating apps or plugins to a newer version, running Capawesome CLI commands, or MCP servers other than Capawesome.
What it needs
About 5k tokens when loaded.
What this skill does
Capawesome MCP Server Connect an MCP client to the hosted Capawesome MCP server for always-current documentation search and Capawesome Cloud management. The server is hosted by Capawesome — there is nothing to install and nothing to keep up to date: It serves two things: Documentation — search and read the current Capawesome documentation and blog. No token required. This is always more up to date than any reference file bundled with a skill. Capawesome Cloud — manage apps, builds, deployments, channels, devices, environments, certificates, and jobs. Requires an API token. Prerequisites 1. An MCP client: Claude Code, Claude Desktop, Cursor, VS Code, or any other client that implements the Model Context Protocol. 2. For Capawesome Cloud tools only: a Capawesome Cloud account and an API token. Agent Behavior Guide step-by-step. Walk the user through the process one step at a time. Never present multiple unrelated questions at once. Auto-detect before asking. Detect the MCP client from the project and environment before asking the user which one they use. Never ask for a token unless Cloud tools are wanted. The documentation tools work without authentication. Only start the token flow when the user wants Capawesome Cloud management. Never write a token into a file that is tracked by Git. See Handling Tokens. Procedures Step 1: Determine Which Toolsets Are Needed Ask the user which of the following they want, and register only that: 1. Documentation only — search and read the Capawesome documentation. No token needed. Use ?toolsets=docs (the default when no query parameter is given). 2. Documentation and Capawesome Cloud — the full surface. Requires a token. Use ?toolsets=all. This is what most setups want. 3. A specific subset — read references/toolsets.md and pick the toolsets matching the user's task. Fewer tools take up less context and make the client pick the right tool more often. If the user is unsure, recommend option 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills capawesome-team/capawesome-mcp