MCP.Market

Capawesome MCP server

online · 100% uptime
by capawesome.io·io.capawesome/mcp·v0.0.2·2 stars
No reviews yet

The official MCP server for Capawesome documentation and Capawesome Cloud.

A90/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A90/100

full report

Adoption
Growing

2 stars34 downloads/wk

Reviews

Write one

Nobody has reviewed Capawesome yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Capawesome tools (3)

write = sends, deletes, buys or posts
  • get_doc_pageFree

    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_postsFree

    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.

  • search_docsFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • Live reliabilityremote reachable in 1247ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 37 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 90/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Capawesome compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
90/100
higher than 83% of 48,243 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
295 ms
faster than 52% of 30,027 servers
GitHub stars
2
more than 75% of 28,706 servers
Downloads a week
34
more than 23% of 12,306 servers with a package

What its tools let an agent do: 3 read

Install Capawesome in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.capawesome.io/mcp
Add to Cursor

What the publisher says

From the Capawesome repository's README, as published. We do not edit it. Read it on GitHub

Capawesome MCP Server

The official MCP server for Capawesome. It gives AI assistants the current Capawesome documentation — plugins, Capawesome Cloud, Capawesome Insiders and the CLI — and, with an API token, the Capawesome Cloud management API for apps, channels, builds, deployments and more.

Maintained by Capawesome.

Endpoint

The server is hosted and ready to use:

https://mcp.capawesome.io/mcp

The documentation tools need no account and no token. The Capawesome Cloud tools are only available when the request carries an API token — see Authentication.

Installation

Claude Code

For the documentation tools, no token is needed:

claude mcp add --transport http capawesome https://mcp.capawesome.io/mcp

To add the Capawesome Cloud tools, pass your API token as a bearer header and select the toolsets:

claude mcp add --transport http capawesome "https://mcp.capawesome.io/mcp?toolsets=all" \
  --header "Authorization: Bearer YOUR_TOKEN"

Claude Desktop / Claude.ai

Go to Settings → Connectors → Add custom connector and enter:

  • Name: Capawesome
  • URL: https://mcp.capawesome.io/mcp

Cursor

Or add .cursor/mcp.json to your project:

{
  "mcpServers": {
    "capawesome": {
      "url": "https://mcp.capawesome.io/mcp"
    }
  }
}

VS Code

Install in VS Code

Or add .vscode/mcp.json to your project:

{
  "servers": {
    "capawesome": {
      "type": "http",
      "url": "https://mcp.capawesome.io/mcp"
    }
  }
}

Windsurf

Add the server to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "capawesome": {
      "serverUrl": "https://mcp.capawesome.io/mcp"
    }
  }
}

Zed

Add the server to your Zed settings.json:

{
  "context_servers": {
    "capawesome": {
      "url": "https://mcp.capawesome.io/mcp"
    }
  }
}

Any client via npx

Clients that cannot connect to a remote server over HTTP can run this package, which proxies stdio to the hosted server:

{
  "mcpServers": {
    "capawesome": {
      "command": "npx",
      "args": ["-y", "@capawesome/mcp"],
      "env": {
        "CAPAWESOME_TOKEN": "your-token"
      }
    }
  }
}

Requires Node.js 22 or later. Omit env to use the documentation tools only.

Authentication

Create an API token in the Capawesome Cloud Console and pass it to the server.

When connecting over HTTP, send it as an Authorization: Bearer header. When running this package, set the CAPAWESOME_TOKEN environment variable and the proxy sends the header for you.

Without a token, only the documentation tools are registered — the Capawesome Cloud tools are absent, not merely hidden.

Configuration

These environment variables configure the proxy. They apply to this package only; over HTTP, use the equivalent header and query parameters.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Capawesome: common questions

Is Capawesome MCP server safe?
Yes, by our scan: it is graded A (90/100). Read the Capawesome safety report
How do I install Capawesome?
It runs remotely at mcp.capawesome.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Capawesome need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Capawesome maintained?
The last commit was 58 days ago (2026-09-08). The latest release is v0.0.2.
Is Capawesome up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Capawesome compare with other MCP servers?
safety score 90/100 (higher than 83% of 48,243 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from capawesome.io →