Capawesome MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPAWESOME_TOKEN | No | API token, sent as Authorization: Bearer. Optional; without it only the documentation tools are available. | |
| CAPAWESOME_MCP_URL | No | Override the endpoint. For development only. | |
| CAPAWESOME_MCP_READONLY | No | Set to 'true' to skip every tool that writes or deletes, sent as ?readonly=true. | false |
| CAPAWESOME_MCP_TOOLSETS | No | Comma-separated toolsets to register, sent as ?toolsets=. Use 'cloud' for every Capawesome Cloud toolset or 'all' for everything. Defaults to 'docs'. | docs |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search the Capawesome documentation, guides and blog by keyword. Use this first for any question about Capawesome SDKs (Capacitor and Cordova plugins such as Live Update, NFC, Biometrics), Capawesome Cloud (live updates, native builds, app store publishing, automations), Capawesome Insiders or the Capawesome CLI — the answer is almost always documented, and guessing plugin APIs or CLI flags produces broken code. Returns the best matching page sections with |
| get_doc_pageA | Read the full source markdown of a Capawesome documentation or blog page. Use this after |
| list_blog_postsA | List the 20 most recent posts from the Capawesome blog, newest first. Use this when the question is about what is new — recent releases, announcements, monthly updates, deprecations or newly published guides. Returns |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct job: search_docs finds relevant pages by keyword, get_doc_page retrieves the full content of a known URL, and list_blog_posts surfaces recent blog posts. The descriptions explicitly cross-reference each other to prevent confusion, so an agent should not struggle to pick the right one.
All tool names follow the same verb_noun snake_case pattern: search_docs, get_doc_page, and list_blog_posts. The verbs (search, get, list) and nouns (docs, doc_page, blog_posts) align with each tool's function, making the naming predictable and readable.
Three tools is a well-scoped set for a documentation/blog access server: one for discovery, one for retrieval, and one for recency browsing. Each tool earns its place, and the count is within the typical 3-15 range for a focused server.
The set covers the core documentation workflow completely: search_docs finds content, get_doc_page reads full pages, and list_blog_posts handles recent announcements. The only minor gap is that list_blog_posts has no pagination beyond the 20 most recent posts, though search_docs can still locate older content.