CometChat is automatable through its API

CometChat is automatable today through its REST API. Every app API request sends the API key in the lowercase apikey header. The app host is https://APPID.api-REGION.cometchat.io/v3. Calls use https://APPID.call-REGION.cometchat.io/v3 and the same header. A fullAccess key can create, update, and delete users, groups, and messages, and must stay on a server. An authOnly key can create users and auth tokens and is described as a demo key. Production clients log in with an auth token created by POST /users/UID/auth_tokens. Some message calls also send onBehalfOf. Management APIs use a different host, https://apimgmt.cometchat.io, and key and secret headers instead of apikey. CometChat also publishes an MCP server at https://mcp.cometchat.com/mcp. The docs say it is read-only, needs no account or API key, and exposes four tools that search docs and return implementation bundles. It does not take a tenant API key. GitHub reported cometchat/docs-mcp unarchived, Apache-2.0, and pushed on 2026-09-22. The docs index at /llms.txt lists the documentation pages. Connector catalogs were not opened. Computer-use viability is unassessed. The API scores 7. The MCP server scores 4 because it is an official documentation assistant, not an interface to an app's users or messages. The API is the best path.

Best path today: api · Overall automatability: 7/10