Docs MCP

What cometchat/docs-mcp does

The cometchat/docs-mcp MCP server gives coding agents a structured way to consult CometChat’s first-party documentation. Its coverage includes SDK guides, UI Kit references, REST API material, and OpenAPI specifications for chat, voice, video, and moderation use cases.

The server is intended for implementation questions rather than application data access. An agent can use it to find setup instructions, compare documentation for supported frameworks, retrieve reference material, or obtain a prepared recipe for a known scenario. Supported implementation contexts mentioned by the project include React, React Native, Flutter, iOS, Android, JavaScript, and no-code website embeds.

How it works

Clients connect over Streamable HTTP, with SSE support, through https://mcp.cometchat.com/mcp. The service is stateless and does not maintain user-specific state. A public health check is available at https://mcp.cometchat.com/health.

For documentation search, the server uses an SQLite FTS5 index built from CometChat’s documentation repository. That index is rebuilt when the source repository’s main branch receives a push. Full pages are fetched as Markdown from CometChat documentation URLs or relative paths. Curated bundles contain prerequisites, installation commands, configuration details, and working code, and include a last-verified date; the README says these bundles are checked against live SDK versions quarterly.

Setup and configuration

Hosted use requires adding the MCP URL to a compatible client. Cursor and Windsurf can use the following server entry:

{
  "mcpServers": {
    "cometchat": {
      "url": "https://mcp.cometchat.com/mcp"
    }
  }
}

Claude Desktop can add the same endpoint through its connector settings. VS Code Copilot Agent supports the URL with HTTP transport, and Claude Code can register it with claude mcp add --transport http cometchat https://mcp.cometchat.com/mcp.

Local development requires cloning the separate CometChat documentation repository, installing dependencies with npm install, setting DOCS_REPO to that checkout, building the index with npm run build:index, and starting the project with npm run dev. The local server defaults to http://0.0.0.0:3000, with /mcp as the MCP endpoint and /health as the health route.

Tools and capabilities

The four exposed tools are:

• search_cometchat_docs: Finds ranked snippets with titles and direct links, optionally filtered by version.
• fetch_cometchat_doc_page: Retrieves a complete documentation page as Markdown using a URL or relative path.
• get_cometchat_implementation_bundle: Returns a named scenario bundle with prerequisites, commands, configuration, and example code.
• list_cometchat_bundles: Lists available bundles with identifiers, titles, frameworks, and verification dates.

The server also publishes resources for orientation and common recipes, including UI Kit quickstarts, messaging basics, moderation, multi-tenant chat, presence, typing indicators, and widget embedding. All four tools are read-only and declare structured output schemas.

Limitations and notes

The server only reads public CometChat documentation; it does not authenticate against an application or modify project data. The code it helps produce still requires CometChat application credentials such as an App ID, Auth Key, and Region. Those values are needed for the resulting integration, not for connecting to the cometchat/docs-mcp MCP server itself. The available documentation and bundles may change as the source repository and SDK versions are updated.

Getting started with this cometchat/docs-mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.