WhatsApp 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| personal_system_configurationB | Report whether this isolated WhatsApp adapter has its required configuration; this does not claim an upstream connection. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. Its purpose is narrow and explicitly stated, making selection trivial.
The single tool name uses predictable snake_case, so there is no inconsistency across tools. It is a noun phrase rather than a verb_noun pattern, but that is a minor deviation for a one-tool set.
One tool is an extreme mismatch for a WhatsApp MCP server, which would normally need messaging, contact, and chat operations. A lone configuration check cannot meaningfully serve the apparent domain.
The surface lacks any send, receive, list, or manage operations for WhatsApp messages, chats, contacts, or media. Only a configuration report is present, leaving the domain severely uncovered.