Zappy 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusB | Check WhatsApp client connection status |
| list_allowedB | List all allowed recipients with their permissions (canSend, canRead) |
| list_chatsA | List all WhatsApp chats with their IDs and permissions. Use this to find chat IDs for config.json setup. |
| send_messageA | Send a WhatsApp message to an ALLOWED phone number or group. Will fail if recipient is not in the allowed list. |
| get_messagesB | Get recent messages from a chat. Only works for chats with canRead permission. |
| delete_messageA | Delete a message. Requires canDelete permission. Can only delete messages sent by you. |
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: delete_message removes messages, get_messages retrieves messages, get_status checks connection, list_allowed shows recipients, list_chats enumerates chats, and send_message sends messages. The descriptions reinforce these distinct roles, making misselection unlikely.
All tools follow a consistent verb_noun naming pattern (e.g., delete_message, get_messages, send_message). There are no deviations in style or convention, making the set predictable and easy to understand at a glance.
With 6 tools, the set is well-scoped for managing WhatsApp interactions, covering core operations like messaging, chat/recipient listing, status checks, and deletions. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool surface covers essential CRUD-like operations for WhatsApp messaging (send, get, delete) and administrative tasks (list chats, list allowed recipients, check status). A minor gap exists in lacking update or permission modification tools, but agents can work around this for basic workflows.