WhatsApp MCP Stream
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | info | |
| MEDIA_DIR | No | ||
| TRANSPORT | No | MCP transport mode | stdio |
| STORE_PATH | No | ||
| SESSION_DIR | No | ||
| SETTINGS_PATH | No | ||
| MEDIA_PUBLIC_BASE_URL | No | ||
| MCP_HTTP_ENABLE_JSON_RESPONSE | No | 1 |
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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_qr_codeA | Get the latest WhatsApp QR code as an image for authentication |
| check_auth_statusA | Check if the WhatsApp client is authenticated and ready |
| logoutA | Logout from WhatsApp and clear the current session |
| force_resyncA | Force a full WhatsApp resync (clears app state and reconnects). |
| search_contactsA | Search WhatsApp contacts by name or phone number. |
| resolve_contactA | Resolve a contact by name or phone number (returns best matches). |
| get_contact_by_idA | Get contact details by JID. |
| get_profile_picA | Get profile picture URL for a contact or group JID. |
| get_group_infoA | Get group metadata and participants by group JID. |
| list_chatsC | Get WhatsApp chats, optionally filtered and sorted. |
| list_system_chatsA | List system chats (status/protocol events). |
| list_groupsB | List group chats only. |
| get_chat_by_idC | Get WhatsApp chat metadata by JID. |
| get_direct_chat_by_contact_numberA | Get direct WhatsApp chat JID by contact phone number (less reliable, use get_chat_by_id if JID is known). |
| get_chat_by_contactA | Resolve a contact by name or phone number and return the chat metadata. |
| analyze_group_overlapsB | Find members that appear across multiple groups and return overlap details. |
| find_members_without_direct_chatA | Find group members that do not have a direct chat with you. |
| find_members_not_in_contactsC | Find group members that are not in your contacts. |
| run_group_auditA | Run a combined group-membership audit (overlaps, no direct chat, not in contacts). |
| list_messagesB | Get WhatsApp messages from a specific chat. |
| get_message_by_idA | Get a specific WhatsApp message by its ID. |
| search_messagesA | Search messages by text, optionally within a specific chat. |
| get_message_contextA | Get recent messages around a specific message ID within its chat (context accuracy depends on fetch limit). |
| get_last_interactionA | Get the most recent message involving a specific contact or group JID. |
| send_messageB | Send a WhatsApp text message to a person or group. |
| send_mediaB | Send media (image, video, document, audio) via WhatsApp. |
| download_mediaA | Download media from a WhatsApp message and return its content. |
| pingD | – |
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 28 tools
Most tools have clear distinct purposes, but there is overlap among analyze_group_overlaps, find_members_not_in_contacts, find_members_without_direct_chat, and run_group_audit, as the latter combines the first three. Additionally, ping lacks a description, causing ambiguity.
All tool names follow a consistent verb_noun pattern using lowercase and underscores, e.g., get_chat_by_contact, list_chats, send_message. There are no mixed conventions or style inconsistencies.
With 28 tools, the set is somewhat heavy for a WhatsApp MCP server, but the variety of operations (auth, chats, messages, contacts, groups, media) justifies the count. It slightly exceeds the typical ideal range but remains acceptable.
The tool set covers common operations like reading chats, sending messages, and managing groups, but lacks lifecycle operations such as creating/deleting groups, adding/removing members, managing contacts, or deleting messages. This leaves notable gaps for full workflow coverage.