Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CAPAWESOME_TOKENNoAPI token, sent as Authorization: Bearer. Optional; without it only the documentation tools are available.
CAPAWESOME_MCP_URLNoOverride the endpoint. For development only.
CAPAWESOME_MCP_READONLYNoSet to 'true' to skip every tool that writes or deletes, sent as ?readonly=true.false
CAPAWESOME_MCP_TOOLSETSNoComma-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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 title, url, snippet, section and, for a hit inside a page, the parentTitle and parentUrl of that page. The same results are attached as structured content. Do not use this to read a full page: call get_doc_page with a url from these results. Do not use it to browse recent announcements or release notes: use list_blog_posts. Do not use it for anything about a concrete app, build, channel or deployment in Capawesome Cloud: those live behind the cloud_* tools.

get_doc_pageA

Read the full source markdown of a Capawesome documentation or blog page. Use this after search_docs to read a page end to end before writing code against a plugin API, a CLI command or a Capawesome Cloud workflow — snippets from search results are deliberately short and regularly omit required configuration steps. Returns the page title, its URL and the page markdown including code samples, as it is authored but without the build metadata. Do not use this to find a page: it needs the exact URL or path, so run search_docs (or list_blog_posts for articles) first. Do not use it for pages outside capawesome.io.

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 title, description, date, categories and url per post; pass a url to get_doc_page to read the whole article. Do not use this to answer a topic question: the feed only carries the newest posts, so search the documentation and the blog archive with search_docs instead.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.8/5.0

Scored across 3 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues