whatsapp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_chatsA | List WhatsApp chats, most recently active first. kind: 'dm', 'group', or omit for both. |
| list_messagesA | Read messages in one chat, oldest first. after/before accept '7d', '24h', '2w', or an ISO date such as 2026-08-01. |
| search_messagesA | Search message text, newest first. Matches a literal substring. |
| get_chat_contextB | Show the messages surrounding one message, to expand a search hit. |
| list_contactsC | List known contacts and named group members. |
| get_group_membersA | List members of a group chat, with admin flags. |
| statsA | Database health: source path, counts, date range, and whether sending is on. |
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 has a distinct retrieval role: chats, chat-scoped messages, full-text search, context expansion, contacts, group membership, and database health. The potential overlaps among list_messages, search_messages, and get_chat_context are clearly separated by their descriptions.
Most tools follow a snake_case verb_noun pattern like list_chats, list_messages, and search_messages. The lone 'stats' breaks the verb_noun convention, and get_group_members could have been list_group_members for stricter parallelism.
With seven tools, the server is well-scoped and each tool addresses a distinct need for inspecting WhatsApp data. No tool feels redundant or extraneous.
The read/search workflow is well covered: chats, messages, search, context, contacts, group members, and health checks. The main gaps are direct single-message lookup and any send/manage operations, but for a read-only database inspection surface these are minor and workaroundable.