WhatsApp Cloud API MCP server by Kapso
WhatsApp Cloud API MCP server by Kapso. The whatsapp by kapso mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.
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.
Everything the assistant can do here goes through one of these:
search_cometchat_docs — Search across SDK guides, UI Kit references, REST API documentation, and OpenAPI specs. Returns ranked snippets with titles + direct links. Optionalfetch_cometchat_doc_page — Fetch the full content of any documentation page as markdown by URL or relative pathget_cometchat_implementation_bundle — Return a curated implementation bundle for a named scenario — prerequisites, install commands, configuration, working codelist_cometchat_bundles — List every available implementation bundle (identifier, title, framework, last-verified date) for discoveryYou will need 2 environment variables: DOCS_BASE_URL, INDEX_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. WhatsApp By Kapso's toolset — search_cometchat_docs, fetch_cometchat_doc_page, get_cometchat_implementation_bundle and 1 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search_cometchat_docs | Search across SDK guides, UI Kit references, REST API documentation, and OpenAPI specs. Returns ranked snippets with titles + direct links. Optional version filter. |
| fetch_cometchat_doc_page | Fetch the full content of any documentation page as markdown by URL or relative path. |
| get_cometchat_implementation_bundle | Return a curated implementation bundle for a named scenario — prerequisites, install commands, configuration, working code. |
| list_cometchat_bundles | List every available implementation bundle (identifier, title, framework, last-verified date) for discovery. |
{
"mcpServers": {
"cometchat": {
"url": "https://mcp.cometchat.com/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DOCS_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| INDEX_PATH | Filesystem location the server is allowed to use. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.