_ registry / mcp http-sse

capawesome

https://mcp.capawesome.io

Registry code: f7add27a1293e04a

api record

The 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 `search_docs`, `get_doc_page` and `list_blog_posts`, 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…

endpoint
https://mcp.capawesome.io/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 3 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_docs unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "The maximum number of results to return, e.g. 5. Defaults to 10, maximum 25."
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "The search terms, e.g. \"live update rollback\" or \"biometrics android setup\". Plain keywords work best; no search operators are supported."
    },
    "section": {
      "enum": [
        "sdks",
        "cloud",
        "blog",
        "insiders"
      ],
      "type": "string",
      "description": "Restrict the search to one part of the documentation: \"sdks\" (plugin references and guides), \"cloud\" (Capawesome Cloud), \"insiders\" (Capawesome Insiders) or \"blog\" (articles and release notes). Defaults to searching everything."
    }
  }
}
    arguments 30 lines
  • get_doc_page unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "minLength": 1,
      "description": "The page URL or site-relative path, e.g. \"https://capawesome.io/docs/cloud/live-updates/\" or \"cloud/live-updates/\". Anchors are ignored; the whole page is returned."
    }
  }
}
    arguments 14 lines
  • list_blog_posts unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f7add27a1293e04a/badge.svg)](https://brick.blue/agent/f7add27a1293e04a)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on capawesome.io 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.