CometChat's first-party MCP server. Connect Claude, Cursor, Windsurf, VS Code Copilot, Codex, or any other Model Context Protocol–compatible agent and integrate CometChat into your app from natural-language prompts.

Ask the agent: "add a chat tab where users can DM each other" — it reads CometChat's documentation, picks the right components for your stack, and writes the integration code.

Read-only. No account, no API key, no authentication required.

Quick install

Config snippet (Cursor / Windsurf / generic MCP clients)

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

Usage

After connecting, prompt your agent with any of these:

• "How do I install the React UI Kit in my Vite project?"
• "Walk me through multi-tenant chat for a Next.js SaaS where workspaces are isolated."
• "Show me how to add presence indicators and typing dots to my iOS conversation list."
• "Set up content moderation so banned words are blocked before delivery."
• "Build a no-code chat widget for my Webflow site."
• "What's the rate limit for sending messages, and what error code do I get when I hit it?"

The agent reads CometChat's documentation, pulls the relevant implementation bundle, and writes the integration code into your project.

Tools

All three carry readOnlyHint: true and a title annotation. Names are ≤ 64 characters. Descriptions describe contracts only — no behavioral instructions to the agent, no cross-tool routing, no marketing language.

Resources

How it works

1. You prompt your agent in natural language.
2. The agent reads the orientation skill (cometchat://skills/overview) to understand which tool/bundle fits your request.
3. For top scenarios, the agent pulls a curated implementation bundle — ready-to-run code with prerequisites, install commands, configuration, and working examples.
4. For long-tail questions, the agent searches CometChat's docs and reads specific reference pages.
5. The agent writes the code into your project, using the bundle as the source of truth and your project structure as the constraint.

CometChat in 30 seconds

CometChat is a real-time communications platform for adding chat, voice, and video calling to web and mobile apps. Used in production across SaaS, marketplaces, gaming, healthcare, education, and creator platforms.

• Free tier: first 100 monthly active users, no credit card required.
• SDKs: JavaScript, React Native, iOS, Android, Flutter.
• UI Kits: React, React Native, iOS, Android, Flutter, Angular, Vue.
• No-code: chat widget for any HTML site.
• Sign up: app.cometchat.com — you'll need an App ID, Auth Key, and Region to build with the code the agent writes.

Server identity

Architecture

Your agent (Claude / Cursor / Windsurf / …)
        ↓ MCP over Streamable HTTP
        ↓
  mcp.cometchat.com/mcp  (this server)
        ↓
  ├── search_cometchat_docs     → SQLite FTS5 index of cometchat/docs
  ├── fetch_cometchat_doc_page  → cometchat.com/docs/*.md (first-party)
  └── get_cometchat_implementation_bundle → bundled markdown recipes

• Stateless server, single universal endpoint, no user-specific state.
• Search index rebuilds from github.com/cometchat/docs on every push to that repo's main branch.
• Implementation bundles carry a last_verified date and are re-checked against live SDK versions quarterly.

Local development

# Clone the docs repo (used to build the search index)
git clone --depth 1 https://github.com/cometchat/docs.git ../cometchat-docs-repo

# Install + build the FTS index + run the server
npm install
DOCS_REPO=../cometchat-docs-repo npm run build:index
npm run dev

# Run the test suite (36 tests across validation, truncation, bundles, tools, resources, fetch)
npm test

The server listens on http://0.0.0.0:3000 by default. Health probe at GET /health, MCP endpoint at POST /mcp.

Inspect with the MCP Inspector

npx @modelcontextprotocol/inspector
# add server: http://localhost:3000/mcp

You should see all 3 tools with readOnlyHint: true and all 11 resources.

Repo layout

docs-mcp/
├── src/
│   ├── server.ts                  # MCP server entry, transport, tool dispatch
│   ├── tools/{search,fetch,bundle}.ts
│   ├── search/sqlite.ts           # SQLite FTS5 client
│   ├── bundles/loader.ts          # markdown bundle store
│   ├── resources/registry.ts      # skill + bundle resources
│   └── lib/{errors,truncate,validation,logger}.ts
├── scripts/build-index.ts         # builds SQLite FTS5 index from cometchat/docs
├── bundles/                       # 10 curated implementation bundles
├── skills/overview.md             # agent orientation skill
├── tests/                         # vitest suite
├── .claude-plugin/
│   ├── plugin.json                # Claude Code plugin manifest
│   └── marketplace.json           # Claude Code marketplace manifest
├── .codex-plugin/plugin.json      # Codex plugin manifest
├── .cursor-plugin/plugin.json     # Cursor Marketplace manifest
├── .mcp.json                      # MCP config (Claude Code auto-discovery)
├── mcp.json                       # Open Plugins standard manifest
└── assets/logo.svg                # CometChat logo

Configuration

Deployment

See DEPLOY.md for container build, environment, and platform notes.

Marketplaces

The same server URL is listed across multiple agent marketplaces:

Support

• Issues / feedback: open an issue in this repo.
• CometChat support: [email protected].
• Live MCP status: curl https://mcp.cometchat.com/health returns {"status":"ok"} when healthy.

Contributing

PRs welcome — especially:

• New implementation bundles for under-served scenarios (drop a markdown file in bundles/ with the required frontmatter).
• Bundle refreshes when SDK versions change (last_verified date in the bundle's frontmatter triggers a CI warning if older than 6 months).
• Tool improvements behind the existing read-only contract.

Out of scope today:

• Tools that write to a customer's CometChat app (separate authenticated connector, on the roadmap).
• Mixed read/write tools (Anthropic auto-rejection rule).

Privacy

The CometChat MCP server is read-only and requires no account, API key, or authentication. It serves only CometChat's public documentation and does not request, store, or transmit your code, prompts, or personal data. Standard request metadata (such as IP address) may be processed transiently for rate limiting and abuse prevention.

For full details, see CometChat's privacy policy: cometchat.com/legal-privacy-policy.

License

Apache-2.0. See LICENSE.