WhatsApp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | Yes | Path to the src directory of the project, required for the Python interpreter to find the whatsapp_mcp package. | |
| WHATSAPP_HEADLESS | No | Whether to run the browser in headless mode. Set to 'false' to show the browser window for scanning the QR code. | false |
| WHATSAPP_PROFILE_DIR | Yes | Absolute path to the directory where the WhatsApp Web session profile (e.g., authentication data) will be persisted. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_auth_statusB | Open WhatsApp Web if needed and report whether login is complete. |
| wait_until_readyB | Wait until WhatsApp Web is fully authenticated and ready for use. |
| list_recent_chatsC | List the most recent chats visible in WhatsApp Web. |
| send_messageC | Send a WhatsApp message using either a phone number or an existing chat name. |
| get_recent_messagesC | Read recent messages from a chat identified by either a phone number or a chat name. |
| shutdown_browserA | Close the browser context and stop the WhatsApp automation session. |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: authentication status, message retrieval, chat listing, message sending, session shutdown, and readiness waiting. The descriptions make it unambiguous which tool to use for each task.
All tools follow a consistent verb_noun pattern (e.g., get_auth_status, send_message, shutdown_browser) with snake_case throughout. The naming is predictable and readable across all six tools.
Six tools is well-scoped for a WhatsApp automation server, covering core operations like authentication, messaging, chat management, and session control without being too sparse or bloated. Each tool earns its place in the workflow.
The toolset covers essential WhatsApp Web operations (authentication, messaging, chat listing) and session lifecycle (shutdown, readiness). Minor gaps might include advanced features like media handling or group management, but core workflows are well-supported.