zaileys-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZAILEYS_PHONE | No | Phone number (E.164 digits) required for pairing-code login | |
| ZAILEYS_TOOLS | No | Tool strategy: progressive, full, core, or comma-list | progressive |
| ZAILEYS_SESSION | No | Session id; auth persists under ./.zaileys/auth/<id> | mcp |
| ZAILEYS_READONLY | No | Set to true to expose only read tools (agent can't send) | false |
| ZAILEYS_ALLOWLIST | No | Comma-separated numbers/JIDs to restrict outbound tools | |
| ZAILEYS_AUTH_TYPE | No | Authentication type: qr or pairing | qr |
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 |
|---|---|
| connection_statusA | Get the WhatsApp connection state (connected/connecting/disconnected) and the active account. |
| meA | Return the connected WhatsApp account (jid, number, name). |
| check_numberB | Check whether phone numbers are registered on WhatsApp. |
| list_chatsC | List recent chats from the store. |
| get_messagesB | Fetch recent messages for a chat from the store, newest first. |
| get_profileB | Fetch a contact/group profile picture URL and status text. |
| send_textB | Send a text message. Supports bold, italic, |
| send_mediaB | Send image/video/audio/document by URL or base64. |
| send_locationC | Send a location pin. |
| reactC | React to a message (empty emoji removes the reaction). |
| chat_mark_readB | Mark a chat as read (blue ticks). |
| send_typingC | Show the typing indicator in a chat. |
| group_metadataB | Get a group subject, description, and participants (with admin flags). |
| find_toolsA | Discover more WhatsApp tools that are not currently active. Call this FIRST whenever you need an action or data that the visible tools do not cover (managing groups, communities, newsletters, privacy, profile, business, deleting/forwarding/pinning messages, etc.) — this account has many more capabilities than the tools shown right now. Pass a short description of what you need (or a category: messaging, chat, group, community, newsletter, presence, profile, contact, privacy, business, account); matching tools become callable immediately after. |
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 14 tools
Each tool has a clearly distinct purpose, covering different actions like sending various message types, reacting, checking status, and managing chats. There is no overlap or ambiguity.
Most tools follow a verb_noun pattern (e.g., send_media, list_chats), but 'me' and 'react' deviate, and 'group_metadata' uses noun_noun. Overall, the pattern is mostly consistent.
14 tools is well-scoped for a WhatsApp integration, covering messaging, media, reactions, typing, group info, account status, and more. Not too few or too many.
The static set lacks some common operations like group creation or message deletion, but the find_tools mechanism can dynamically activate missing tools. Therefore, notable gaps exist but are mitigable.