Koskamo

Capawesome MCP

The official MCP server provided by Capawesome that enables AI agents to access Capawesome documentation and interact with the Capawesome Cloud management API for tasks like live updates, native builds, and app store publishing.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Capawesome MCP logo, by CapawesomeVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Capawesome
MCP endpoint (Streamable HTTP)
https://mcp.capawesome.io/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

3 of 3 have a description · 3 of 3 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to capawesome.io ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Access Capawesome documentation
  • Manage Capawesome Cloud services
  • Retrieve plugin and SDK information

Source and maintenance

Vendor evidenceRegistry 0.0.2
Maintenance checked

Protocol and capabilities

Server
capawesome 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

The official MCP server for Capawesome. It serves the Capawesome documentation and blog from capawesome.io — the Capawesome plugins for Capacitor and Cordova, Capawesome Cloud (Live Updates, Native Builds, App Store Publishing), Capawesome Insiders and the Capawesome CLI — through `search_docs`, `get_doc_page` and `list_blog_posts`, and it manages Capawesome Cloud itself through the `cloud_*` tools. The `cloud_*` tools are registered only when the request carries a Capawesome Cloud token in the `Authorization: Bearer <token>` header (create one at https://console.cloud.capawesome.io/settings/tokens); add `?toolsets=cloud` to the endpoint URL to select every Cloud toolset, a named toolset such as `cloud-apps` to select one, `?toolsets=all` for everything, and `readonly=true` to drop every tool that writes or deletes. Without a token the documentation tools are served regardless of the requested toolsets. For Capacitor itself — the CLI, the `capacitor.config` file, the official and community plugins and the native iOS and Android configuration — use the Capacitor MCP server at https://capacitor-mcp.capawesome.io/mcp; for Ionic Framework UI components use the Ionic Framework MCP server at https://ionic-framework-mcp.capawesome.io/mcp.

Tools

3 advertised

search_docs — Search Capawesome documentation
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

search_docs input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "The maximum number of results to return, e.g. 5. Defaults to 10, maximum 25."
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "The search terms, e.g. \"live update rollback\" or \"biometrics android setup\". Plain keywords work best; no search operators are supported."
    },
    "section": {
      "enum": [
        "sdks",
        "cloud",
        "blog",
        "insiders"
      ],
      "type": "string",
      "description": "Restrict the search to one part of the documentation: \"sdks\" (plugin references and guides), \"cloud\" (Capawesome Cloud), \"insiders\" (Capawesome Insiders) or \"blog\" (articles and release notes). Defaults to searching everything."
    }
  }
}
search_docs output schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "results"
  ],
  "properties": {
    "results": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "title",
          "url",
          "snippet",
          "section"
        ],
        "properties": {
          "url": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "section": {
            "type": "string"
          },
          "snippet": {
            "type": "string"
          },
          "parentUrl": {
            "type": "string"
          },
          "parentTitle": {
            "type": "string"
          }
        },
        "additionalProperties": false
      }
    }
  },
  "additionalProperties": false
}
search_docs annotations
{
  "title": "Search Capawesome documentation",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}
get_doc_page — Read a documentation page
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

get_doc_page input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "minLength": 1,
      "description": "The page URL or site-relative path, e.g. \"https://capawesome.io/docs/cloud/live-updates/\" or \"cloud/live-updates/\". Anchors are ignored; the whole page is returned."
    }
  }
}
get_doc_page annotations
{
  "title": "Read a documentation page",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}
list_blog_posts — List recent blog posts
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

list_blog_posts input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
list_blog_posts annotations
{
  "title": "List recent blog posts",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
482 ms
95th percentile latency
482 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 482 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http capawesome-mcp https://mcp.capawesome.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add capawesome-mcp --url https://mcp.capawesome.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable capawesome-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "capawesome-mcp": {
      "url": "https://mcp.capawesome.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "capawesome-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.capawesome.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start capawesome-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "capawesome-mcp": {
      "type": "http",
      "url": "https://mcp.capawesome.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http capawesome-mcp https://mcp.capawesome.io/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.capawesome.io/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "capawesome-mcp": {
      "serverUrl": "https://mcp.capawesome.io/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Capawesome MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Capawesome MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing