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 整合