WhatsApp MCP Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUTH_TOKEN | Yes | Separate external MCP transport bearer token. | |
| MCP_ALLOWED_HOSTS | No | Allowed MCP HTTP Host values, including the hostname used by your ingress. | |
| WHATSAPP_API_TOKEN | No | Backend HTTP API bearer token, shared only by the proxy and MCP. | |
| MCP_ALLOWED_ORIGINS | No | Explicit browser origins for MCP; empty by default. | |
| MEDIA_ALLOWED_HOSTS | No | Exact trusted external HTTPS media hosts; empty rejects external URL downloads. | |
| WHATSAPP_ADMIN_TOKEN | No | Administrative token for QR, session operations, queue inspection/replay, configuration, and group settings. | |
| MCP_IMAGE_ALLOWED_HOSTS | No | Trusted external image hosts for the MCP legacy URL input. | |
| WHATSAPP_API_TOKEN_FILE | No | Mounted file containing the backend HTTP API bearer token. | |
| WHATSAPP_ALLOWED_ORIGINS | No | Optional trusted browser origins; same-origin management works by default. | |
| WHATSAPP_ADMIN_TOKEN_FILE | No | Mounted file containing the administrative token. |
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 recent community issues