Capawesome

io.capawesome由 capawesome.io 发布官方发布者v0.0.2更新于 Oct 24, 2026

The official MCP server for Capawesome documentation and Capawesome Cloud.

发布方自己的服务:Capacitor Mcp

已验证Streamable HTTP可网页运行云端与基础设施知识与记忆开发者工具

概览

AI 生成的概览

Capawesome 官方 MCP 服务器,让助手搜索和阅读 Capawesome 文档、指南与博客文章,并可选使用 Capawesome Cloud 管理功能

可以做什么
按关键词搜索 Capawesome 文档、指南和博客文章,涵盖 Capacitor 与 Cordova 插件、Capawesome Cloud、Insiders 和 CLI。搜索后阅读文档或博客页面的完整 Markdown 源文。列出最近 20 篇博客文章,含标题、描述、日期、分类和链接。持有 API 令牌时,可使用面向 Capawesome Cloud 管理 API 的 cloud 工具,涵盖应用、通道、构建和部署。
适用场景
在针对 Capawesome 插件或 CLI 命令编写代码时使用,或用于回答关于 Capawesome Cloud、Insiders 及近期发布和公告的问题。仅当你管理 Capawesome Cloud 应用、构建或部署时才添加 Cloud 工具。
运行要求
远程端点 npx 运行 npm 包 @capawesome/mcp,需要 Node.js 22 或更高版本。文档工具无需账号。Capawesome Cloud 工具需要来自 Capawesome Cloud 控制台的 API 令牌,通过 Authorization bearer 请求头或 CAPAWESOME_TOKEN 环境变量发送。
安装前请注意
可选的 Capawesome Cloud 工具可以写入和删除资源;将 CAPAWESOME_MCP_READONLY 设为 true 可跳过这些工具。API 令牌通过 Authorization bearer 请求头或 CAPAWESOME_TOKEN 发送,应妥善保密。端点限制为每个 IP 每分钟 100 次请求,你的 IP 会用于速率限制处理。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Capawesome,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.capawesome%2Fmcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

来源:README.md,提交 9ec4c9b

工具

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.

输入参数limitquery必填section

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.

输入参数url必填

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.

无需输入参数。

版本历史

1
  1. v0.0.2最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Capawesome 集成