Skip to content
CometChat logo

CometChat MCP server

Which servers in the official MCP registry are CometChat's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-09

← Back to CometChat

Whose server it is
  • Registry nameio.github.cometchat/docs-mcppublished by cometchat on GitHub

Published under the GitHub organisation cometchat, the same one cometchat.com links from its homepage. The registry ties that namespace to a GitHub sign-in.

When we asked itchecked 2026-10-09
  • Stateanswerschecked 2026-10-09
  • Tools4
  • Server calls itselfCometChat Docs
  • Server version0.1.6
  • Protocol version2025-06-18

On 2026-10-09 the server answered initialize and tools/list without a sign-in. First answer in 471 ms.

Tools it offers4 tools · read 2026-10-09
  • search_cometchat_docs

    Searches CometChat documentation including SDK guides (JavaScript, React, iOS, Android, Flutter, React Native), UI Kit references, REST API documentation, integration tutorials, and OpenAPI specs. Returns ranked snippets with titles and…

  • fetch_cometchat_doc_page

    Fetches the full content of a single CometChat documentation page by URL or path. Returns the page content as markdown along with title and section metadata. Path can be passed as a full https://www.cometchat.com/docs URL or as a relative…

  • get_cometchat_implementation_bundle

    Returns a curated implementation bundle for a named CometChat integration scenario. Each bundle includes prerequisites, install commands, configuration, working code examples, and common pitfalls. Available bundles cover common…

  • list_cometchat_bundles

    Lists every available CometChat implementation bundle with its identifier, title, target framework, and last-verified date.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "docs-mcp": {
      "type": "http",
      "url": "https://mcp.cometchat.com/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.