chatkazi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHATKAZI_API_KEY | Yes | Your live API key retrieved from your ChatKazi dashboard. | |
| CHATKAZI_BASE_URL | No | The base URL of the API. Defaults to https://api.chatkazi.app/api/v1 if omitted. | https://api.chatkazi.app/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sessionsA | List all WhatsApp sessions connected to the ChatKazi account. |
| start_sessionB | Initialize a new WhatsApp session connection. |
| get_session_statusA | Check the current state of a specific WhatsApp session (e.g., connected, qr_ready). |
| get_session_qrA | Retrieve the QR code pairing link for an initialized session. |
| logout_sessionA | Disconnect and log out a WhatsApp session, clearing its authentication state. |
| send_whatsapp_textA | Send a plain text WhatsApp message to a recipient. |
| send_whatsapp_mediaA | Send a media message (image, video, audio, or document) to a recipient. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action: session management (list, start, status, QR, logout) versus messaging (text, media). No two tools have overlapping purposes, and the descriptors clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_sessions, start_session, send_whatsapp_text). The pattern is uniform and predictable across the set.
Seven tools is well-scoped for a WhatsApp MCP server covering session lifecycle and message sending. Each tool serves a necessary function without redundancy or bloat.
The tool set covers the full session lifecycle (initiate, check status, retrieve QR, log out, list) and both primary message types (text and media). No obvious gaps for the stated domain.