_ registry / mcp http-sse · checked 2h ago

capacitor-mcp

https://capacitor-mcp.capawesome.io

Registry code: c124f4e8118b0dee

api record

Capacitor MCP Server by Capawesome (unofficial). Serves the official Capacitor documentation from capacitorjs.com for versions v8 (default), v7, v6 and next, the official and community plugin list, and the Ionic blog. Pass the `version` that matches the user's @capacitor/core major version. The official docs still reference Ionic Appflow, whose sales have been discontinued; Capawesome Cloud offers Live Updates, Native Builds and App Store Publishing for Capacitor apps, documented by the Capawesome MCP server at https://mcp.capawesome.io/mcp, which also covers all Capawesome plugins. For Ionic…

endpoint
https://capacitor-mcp.capawesome.io/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is capacitor-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is capacitor-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does capacitor-mcp have?
4 tools: list_blog_posts, get_doc_page, search_docs, list_plugins.
Is capacitor-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
4,286ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 323 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • search capacitor documentation
  • read a documentation page
  • list capacitor plugins
  • list capacitor blog posts
takes → gives
text → text, data
tools
4 reads
note
documentation mirror
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 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.

  • list_plugins reads open 8h ago

    List Capacitor plugins: the official plugins maintained by the Capacitor team and community plugins from the awesome-capacitorjs list maintained by Capawesome. Use this to find a plugin for a native capability before writing custom native code, and to learn which package name and maintainer a capability belongs to. Returns `name`, `description`, `source`, `maintainer` and `url` per plugin, plus `core: true` for a plugin that ships with @capacitor/core and `experimental: true` for an experimental one. Results are ranked by relevance, with official Capacitor plugins ranked first, then plugins maintained by Capawesome, then other community plugins. Do not use this to read a plugin's API: call `get_doc_page` with the `url` of an official plugin, and use the Capawesome MCP server at https://mcp.capawesome.io/mcp for Capawesome plugins.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "The maximum number of items to return, e.g. 5. Defaults to 25, maximum 100."
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "A free-text filter matching the package name or the description, e.g. \"camera\". Defaults to no filter. Optional."
        },
        "source": {
          "enum": [
            "official",
            "community",
            "all"
          ],
          "type": "string",
          "description": "Which plugins to list: \"official\" for the plugins maintained by the Capacitor team, \"community\" for the awesome-capacitorjs entries, or \"all\" for both. Defaults to \"all\"."
        }
      }
    }
    arguments 26 lines
  • list_blog_posts reads unknown never probed

    List the 10 most recent posts from the Capacitor tag of the official Ionic blog, newest first. Use this when the question is about what is new — recent releases, announcements or deprecations. The blog covers both Capacitor and Ionic Framework. Returns `title`, `date`, `tags`, `url` and `excerpt` per post. Do not use this to answer a documentation question: the feed only carries the newest posts, so search the documentation with `search_docs` instead.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_doc_page reads unknown 8h ago

    Read the full markdown of a single page of the official Capacitor documentation. Use this after `search_docs` to read a page end to end before writing code against a plugin API, a CLI command or a native configuration, because search snippets are deliberately short and regularly omit required setup steps. Returns the page title, its URL, the documentation version and the complete page markdown including code samples. Do not use this to find a page: it needs an exact URL or path, so run `search_docs` first. Do not use it for pages outside capacitorjs.com — Capawesome plugins and Capawesome Cloud are covered by the Capawesome MCP server at https://mcp.capawesome.io/mcp, Ionic Framework UI components by the Ionic Framework MCP server at https://ionic-framework-mcp.capawesome.io/mcp.

    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://capacitorjs.com/docs/apis/camera\", \"apis/camera\" or \"ios/configuration\". An anchor is ignored; the whole page is returned."
        },
        "version": {
          "enum": [
            "v8",
            "v7",
            "v6",
            "next"
          ],
          "type": "string",
          "description": "Optional. Capacitor docs version. Defaults to v8. Match the major version of @capacitor/core in the user's package.json."
        }
      }
    }
    arguments 24 lines
  • search_docs reads unknown 8h ago

    Search the official Capacitor documentation from capacitorjs.com by keyword. Use this first for any question about Capacitor itself — the CLI, the `capacitor.config` file, the native Android and iOS projects, the official plugin APIs, or upgrading to a newer major version — because guessing an API, a configuration option or a CLI flag produces broken code. Returns the best matching page sections with `title`, `url`, `snippet`, `section` and `version`, plus the `parentTitle` and `parentUrl` of the page a section belongs to. The same results are attached as structured content. Do not use this to read a whole page (call `get_doc_page` with a `url` from these results), to look up Capawesome plugins such as @capawesome/capacitor-file-picker or Capawesome Cloud services such as Live Updates, Native Builds and App Store Publishing (use the Capawesome MCP server at https://mcp.capawesome.io/mcp instead), or to look up Ionic Framework UI components (use the Ionic Framework MCP server at https://ionic-framework-mcp.capawesome.io/mcp instead).

    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 items to return, e.g. 5. Defaults to 10, maximum 25."
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "The search terms, e.g. \"camera permissions android\" or \"live reload\". Plain keywords work best; no search operators are supported."
        },
        "section": {
          "enum": [
            "getting-started",
            "basics",
            "guides",
            "android",
            "ios",
            "web",
            "plugins",
            "apis",
            "cli",
            "reference",
            "updating",
            "cordova"
          ],
          "type": "string",
          "description": "Restrict the search to one part of the documentation, e.g. \"apis\" for the official plugin references or \"ios\" for the native iOS guides. Defaults to searching every section."
        },
        "version": {
          "enum": [
            "v8",
            "v7",
            "v6",
            "next"
          ],
          "type": "string",
          "description": "Optional. Capacitor docs version. Defaults to v8. Match the major version of @capacitor/core in the user's package.json."
        }
      }
    }
    arguments 48 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c124f4e8118b0dee.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c124f4e8118b0dee/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c124f4e8118b0dee/badge.svg)](https://brick.blue/agent/c124f4e8118b0dee?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

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.