WhatsApp MCP
by Dyfintie
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHATSAPP_MCP_URL | No | MCP daemon URL used by the stdio bridge. | http://127.0.0.1:8787/mcp |
| WHATSAPP_OFFLINE | No | Set to "true" to disable WhatsApp network startup for testing. | |
| WHATSAPP_HTTP_PORT | No | Local loopback port for the MCP daemon. Change this if 8787 is occupied and configure WHATSAPP_MCP_URL accordingly. | 8787 |
| WHATSAPP_STATE_DIR | No | Private state directory used by the launcher. Set to a custom absolute private directory if desired. | ~/.whatsapp-mcp-public |
| WHATSAPP_DB_KEY_FILE | No | Path to the database key file. Defaults to database.key under WHATSAPP_STATE_DIR. | database.key under state directory |
| WHATSAPP_TRANSFER_DIR | No | Transfer/media staging directory. Must be tmpfs. | /dev/shm/whatsapp-mcp-UID |
| WHATSAPP_API_TOKEN_FILE | No | Path to the API token file. The daemon and bridge must use the same API-token file. Defaults to api-token under WHATSAPP_STATE_DIR. | api-token under state directory |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues