WhatsApp Groups 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_groupsA | List the WhatsApp groups you may read, with message counts and date range. |
| search_messagesB | Search message text (case-insensitive substring) in allowed groups. group_jid: limit to one group. since: ISO date like 2026-11-01. Newest first. |
| get_messagesB | Read a group's messages in time order. since: ISO date; default returns the latest |
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 3 tools
list_groups is clearly distinct, but search_messages and get_messages both return group message content and could be confused at a glance; the descriptions do clarify (text substring vs. time-ordered read), so boundaries are recoverable.
All three tools follow a clean verb_noun snake_case pattern (list_groups, search_messages, get_messages), making purpose predictable from name alone.
Three tools is minimal but well-matched to a deliberately narrow read-only scope; nothing is redundant, though the surface is close to feeling thin.
Core read workflows (discover groups, browse by time, search text) are covered, but there is no sender/author filtering, no message pagination/cursor controls, and no group metadata lookup; read-only may be intentional but leaves notable gaps for deeper queries.