- Home
- Resources
- Integrations
- CometChat
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
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.
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.
Plug CometChat into Claude in three steps
- 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.
- 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.
- 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.
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 toolsThree 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.
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.
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.
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.
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.
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 connecting CometChat to Claude?
A person reads every message.