Capawesome MCP Server
MCP serverDocs & knowledgeThe official MCP server for Capawesome documentation and Capawesome Cloud.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use Capawesome MCP Server to search docs
From the project's README
As published by capawesome-team/mcp in README.md.
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
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 <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.
| Variable | Purpose |
|---|---|
CAPAWESOME_TOKEN | API token, sent as Authorization: Bearer. Optional; without it only the documentation tools are available. |
CAPAWESOME_MCP_TOOLSETS | Comma-separated toolsets to register, sent as ?toolsets=. Use cloud for every Capawesome Cloud toolset or all for everything. Defaults to docs. |
CAPAWESOME_MCP_READONLY | Set to true to skip every tool that writes or deletes, sent as ?readonly=true. |
CAPAWESOME_MCP_URL | Override 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
- Capacitor MCP Server — unofficial MCP server for the Capacitor documentation, plugin list and blog.
- Ionic Framework MCP Server — unofficial MCP server for the Ionic Framework documentation, components and usage examples.
- Capawesome Cloud Live Updates — ship JavaScript, HTML and CSS changes to your app without an app store review.
- Capawesome Cloud Native Builds — build native iOS and Android apps in the cloud, without a Mac.
- Capawesome Cloud App Store Publishing — submit builds to the Apple App Store and Google Play Store.
Development
npm install
npm run build
npm test
Set CAPAWESOME_MCP_URL to point the proxy at a local server instead of the hosted one:
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.
Tools it offers (3)
What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.
search_docsget_doc_pagelist_blog_posts
Signals
- GitHub stars
- 2
- Last commit
- Sep 2026
Advanced
- Delivery
- mcp MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
io-capawesome-mcp- Source
- github.com/capawesome-team/mcp
- Hosted endpoint
https://mcp.capawesome.io/mcp