Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
The official MCP server for Capawesome documentation and Capawesome Cloud.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.capawesome.io/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"capawesome": {
"command": "npx",
"args": [
"-y",
"@capawesome/mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http capawesome https://mcp.capawesome.io/mcpclaude mcp add capawesome -- npx -y @capawesome/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"capawesome": {
"url": "https://mcp.capawesome.io/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"capawesome": {
"command": "npx",
"args": [
"-y",
"@capawesome/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"capawesome": {
"type": "http",
"url": "https://mcp.capawesome.io/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"capawesome": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@capawesome/mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.capawesome.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain capawesome.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.0.2) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
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"
Go to Settings → Connectors → Add custom connector and enter:
Capawesomehttps://mcp.capawesome.io/mcpOr add .cursor/mcp.json to your project:
{
"mcpServers": { "capawesome": { "url": "https://mcp.capawesome.io/mcp" } } }
Or add .vscode/mcp.json to your project:
{
"servers": { "capawesome": { "type": "http", "url": "https://mcp.capawesome.io/mcp" } } }
Add the server to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": { "capawesome": { "serverUrl": "https://mcp.capawesome.io/mcp" } } }
Add the server to your Zed settings.json:
{
"context_servers": { "capawesome": { "url": "https://mcp.capawesome.io/mcp" } } }
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.
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.
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. |
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.
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.
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.
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
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= with the Ed25519 private key from the password manager and then mcp-publisher publish.
See LICENSE.