Resources · Claude connector

Claude CometChat connectorWhat Claude can do in your CometChat account.

The Claude CometChat connector exposes 3 tools, all 3 for reading and 0 for writing. They search CometChat's public docs and hand Claude a curated recipe. Below: what Claude finds, what it never touches, and why no CometChat login is involved.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when a developer asks Claude for chat

Adding messaging to a product usually starts with a pile of browser tabs: SDK guide, UI Kit reference, REST docs. With this connector, Claude reads that material itself while it answers, picks the pieces that match your stack, and drafts the integration code in your project rather than sending you off to read.

Find the right page fast. You ask how group calls work in the JavaScript SDK: search_cometchat_docs brings back ranked excerpts from guides, UI Kit references, REST docs and OpenAPI specs, each with a direct link.

Read the whole reference, not a snippet. When an excerpt is not enough, fetch_cometchat_doc_page pulls the complete page as markdown, by URL or relative path, so Claude works from the full text.

Start from a tested recipe. For a known scenario, say a Flutter app that needs a basic chat screen, get_cometchat_implementation_bundle returns prerequisites, install steps, configuration and working code. CometChat curates ten of these bundles.

What it does not do: it never logs into your CometChat app, never reads your users or messages, never changes a setting. Everything it reaches is public documentation. It also does not run on its own; nothing fires when a user signs up. For that kind of background job, look at automation tools from the Integrations hub, a different trade altogether.

Vocabulary

Five words before you plug it in

The vocabulary you will meet in Claude's settings.

Connector
The link you set up once between Claude and a service, so Claude can work with that service while it answers your questions.
Tool
One named action a connector gives Claude. Claude chooses the ones it needs by itself, and the directory sheet lists every tool by name.
Authorization
The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and revocable the same way.
Approval
The confirmation Claude waits for in the conversation before it goes ahead with anything that changes an account on your behalf.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service in the first place.
Connect

Plug CometChat into Claude in three steps

  1. 01

    Find CometChat in your settings

    In Claude, open Customize, then Connectors, and look for CometChat in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before members can add it for themselves.

  2. 02

    Start the connection

    Hit Connect on its row. If a service window opens, finish there; CometChat's own docs state the server asks for no account and no API key. A link that breaks is fixed with Disconnect, then a fresh connect.

  3. 03

    Read the screen before you accept

    Whatever screen the service shows, read it before you confirm. It belongs to the service, not to Claude, and it is what defines the reach of the access. You can withdraw that access later from the same place.

Tools

The 3 tools, sorted by what they do

CometChat gives Claude 3 tools: 3 that read your account, 0 that change something in it.

All three read. None of them writes to a CometChat account, and the names stay in English, exactly as Claude displays them.

  • 3 read

What Claude reads (3)

3 tools

Three tools that look things up in CometChat's public documentation.

search_cometchat_docs

Runs a search across CometChat's SDK guides, UI Kit references, REST API pages and OpenAPI specs, and returns the best-ranked excerpts with a direct link to each source page.

When it helps
a React Native developer wants to know where typing indicators are covered before touching the code.
Watch out
it returns excerpts only; the full page comes from fetch_cometchat_doc_page.

Sourcecometchat.com · May 14, 2026 ↗

fetch_cometchat_doc_page

Pulls one complete page of the CometChat documentation, converted to markdown, from either its full URL or its relative path, so Claude can quote and reason over the whole text.

When it helps
a backend engineer pastes a REST reference link and asks Claude to explain every parameter of that endpoint.
Watch out
it reads public pages only, so nothing specific to your own app configuration comes back.

Sourcecometchat.com · May 14, 2026 ↗

get_cometchat_implementation_bundle

Hands Claude a curated recipe for a named scenario: prerequisites, install, configuration and code that already works. Claude then adapts it to your project instead of assembling the steps from scattered pages.

When it helps
a product team needs a first chat screen in a Flutter prototype by the end of the sprint.
Watch out
the recipes cover the scenarios CometChat curated, ten of them; anything outside that list falls back to search.

Sourcecometchat.com · May 14, 2026 ↗

Approvals

What Claude asks before it acts

By default, Claude stops and asks for your go-ahead before any action it takes on an account in your place. Here the question rarely comes up, since the three tools only read public pages.

On a Team or Enterprise workspace, owners decide whether members may let certain actions through without being asked every time. They can also cap what a connector may do for the whole organisation, keeping reading open and closing writing, and that setting binds everyone. Claude works with the rights of the person connected and nothing more. The official read-only versus write-delete label for each tool exists only inside a signed-in account's settings.

Plans

Which plans can use it

Not one of the 819 sheets in the official directory shows availability by plan. That answer, connector by connector, is published nowhere: a real gap in the catalogue.

The general rule is public. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile; desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organisation before members can connect. For the live status, check the CometChat sheet in the official directory from your own account.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you, and nothing starts by itself when a message is sent or a user joins your app.

Only CometChat documents this connector; neither Claude's help centre nor Anthropic's developer docs have a page on it. By default its sheet exposes reading only, which is an observed floor, not a promise. The directory's verification badge is not a security audit either, and Anthropic says on every sheet that it does not control the tools a publisher exposes. Plug in only what comes from a publisher you trust. For another sheet read the same way, see the Claude agility-cms connector page.

Need help

Need help connecting CometChat to Claude?

A person reads every message.

FAQ

Claude CometChat connector: common questions

01What can Claude do with the CometChat connector?
Claude can search CometChat's public documentation, open any reference page in full, and pull a ready implementation recipe for a named scenario. Those three tools cover SDK guides, UI Kit references, REST API docs and OpenAPI specs. In practice you describe the feature you want, such as direct messages or a call button, and Claude gathers the right material and drafts the integration code for your stack. It works on documentation, not on your live CometChat app or its data.
02Can Claude change anything in my CometChat account?
No tool on the sheet is described as writing. All three read public documentation, and CometChat states the server needs neither an account nor an API key, so it has nothing of yours to modify. Keep in mind that a read-only tool list is an observed floor rather than a guarantee: an administrator can open write actions that no public sheet shows. Code Claude writes from a recipe ends up in your own project, which you review and commit yourself.
03Does Claude ask before it acts?
By default, yes: Claude asks for confirmation before any action it carries out on an account on your behalf. With this connector the question barely arises, since every tool only reads public pages. No source describes a confirmation step specific to these tools, so the default rule is the one that applies. On Team and Enterprise workspaces, owners decide whether members can let some actions through without being asked each time.
04Which plans is it available on?
No official source publishes plan availability connector by connector, and none of the directory sheets shows it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions run on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner has to enable each connector first. The sheet in the official directory remains the only place that shows the current status for your account.
05Does Claude see my whole CometChat app?
No. The connector does not sign into your CometChat app at all; it reads the public documentation and curated recipes, and nothing else. Your users, conversations, groups and settings stay outside the chat. More generally, Claude only ever works with the rights of the person connected, and an owner of a Team or Enterprise workspace can restrict what any connector may do for the whole organisation, with no member able to lift that from their own account.
06Why does Claude only cover some frameworks with a full recipe?
Because ready recipes exist only for the ten bundles CometChat curated, including UI Kit quickstarts for React, React Native and Flutter. When your scenario matches one of them, Claude receives prerequisites, install steps, configuration and working code in one go. When it does not, Claude falls back on searching the docs and reading full pages, which still works but means it assembles the steps itself rather than starting from a recipe the publisher prepared.
07Claude or an automation tool for CometChat?
They answer different needs, so pick by task. Claude, through this connector, helps you build: it reads the documentation and writes integration code with you during a conversation, then stops when you stop typing. It does not react to events in your app, such as a new user or a flagged message. Work that has to run in the background on such events belongs to an automation tool. For learning and coding the integration, the connector fits.