Capawesome

io.capawesomePublished by capawesome.ioOfficial publisherv0.0.2Updated Oct 24, 2026

The official MCP server for Capawesome documentation and Capawesome Cloud.

The publisher's own server: Capacitor Mcp

VerifiedStreamable HTTPWeb executableCloud & InfrastructureKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Official Capawesome MCP server that lets an assistant search and read Capawesome documentation, guides and blog posts, with optional Capawesome Cloud management

What you can do
Search Capawesome documentation, guides and blog posts by keyword, covering Capacitor and Cordova plugins, Capawesome Cloud, Insiders and the CLI. Read the full markdown source of a documentation or blog page after searching. List the 20 most recent blog posts with title, description, date, categories and URL. With an API token, use cloud tools for the Capawesome Cloud management API, covering apps, channels, builds and deployments.
When to use it
Use it when writing code against Capawesome plugins or CLI commands, or when answering questions about Capawesome Cloud, Insiders or recent releases and announcements. Add the Cloud tools only if you manage Capawesome Cloud apps, builds or deployments.
Requirements
Remote endpoint at or the npm package @capawesome/mcp via npx, which needs Node.js 22 or later. Documentation tools need no account. Capawesome Cloud tools need an API token from the Capawesome Cloud Console, sent as an Authorization bearer header or the CAPAWESOME_TOKEN environment variable.
Before you install
The optional Capawesome Cloud tools can write and delete resources; set CAPAWESOME_MCP_READONLY to true to skip them. The API token is sent as an Authorization bearer header or CAPAWESOME_TOKEN and should be kept secret. The endpoint is rate limited to 100 requests per minute per IP, and your IP is processed for rate limiting.

Installation

In SourceWeft

  1. Open Capawesome in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.capawesome%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

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:

bash
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:

bash
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

[Install in Cursor]

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

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

VS Code

Install in VS Code

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

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

Windsurf

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

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

Zed

Add the server to your Zed settings.json:

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:

json
{  "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 <token> 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.

VariablePurpose
CAPAWESOME_TOKENAPI token, sent as Authorization: Bearer. Optional; without it only the documentation tools are available.
CAPAWESOME_MCP_TOOLSETSComma-separated toolsets to register, sent as ?toolsets=. Use cloud for every Capawesome Cloud toolset or all for everything. Defaults to docs.
CAPAWESOME_MCP_READONLYSet to true to skip every tool that writes or deletes, sent as ?readonly=true.
CAPAWESOME_MCP_URLOverride the endpoint. For development only.

Tools

The server exposes the documentation tools (search_docs, get_doc_page, list_blog_posts) plus the cloud_* tools for the Capawesome Cloud management API, grouped into toolsets.

See the MCP documentation for the full tool and toolset reference.

Rate limits

The endpoint is limited to 100 requests per minute per IP. Requests over the limit are answered with 429 Too Many Requests; retry after a short wait.

Privacy

Your IP address is processed for rate limiting only. Queries and tool arguments are not stored, not logged beyond Cloudflare's standard edge logs, and never used for training. Your API token is used to authenticate against the Capawesome Cloud API on your behalf and is not stored by the server. See the Privacy Policy for details.

Related

Development

bash
npm installnpm run buildnpm test

Set CAPAWESOME_MCP_URL to point the proxy at a local server instead of the hosted one:

bash
CAPAWESOME_MCP_URL=http://localhost:8787/mcp node dist/index.js

Release

Releases are managed by release-please. Merging its release pull request tags the version, publishes the package to npm and then publishes server.json to the MCP Registry. The version in server.json is bumped by release-please together with package.json, so it never has to be edited by hand. To publish to the registry manually, install mcp-publisher, run mcp-publisher login dns --domain=capawesome.io --private-key=<key> with the Ed25519 private key from the password manager and then mcp-publisher publish.

License

See LICENSE.

Source: README.md at commit 9ec4c9b

Tools

3

search_docs

Search Capawesome documentation

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.

Parameterslimitqueryrequiredsection

get_doc_page

Read a documentation page

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.

Parametersurlrequired

list_blog_posts

List recent blog posts

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.

Takes no parameters.

Version history

1
  1. v0.0.2LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Capawesome integrations

Capacitor Mcp

io.capawesomeOfficial publisher

Unofficial MCP server that gives assistants the official Capacitor docs, plugin lists and Ionic blog posts so they stop guessing APIs and CLI flags.

Streamable HTTPWeb executable
Knowledge & Memory4 toolsOct 24, 2026

Ionic Framework Mcp

io.capawesomeOfficial publisher

Unofficial MCP server that gives an assistant the Ionic Framework v9/v8 docs, component API reference, usage examples and blog.

Streamable HTTPWeb executable
Knowledge & Memory5 toolsOct 24, 2026