HelloHop WhatsApp MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GATEWAY_API_URL | No | Your API base. Defaults to https://api.wagate.dev/v1, the public API. Must be https (http is accepted only for localhost). | https://api.wagate.dev/v1 |
| GATEWAY_API_TOKEN | Yes | The channel's API token. It is never logged. | |
| GATEWAY_ALLOW_SEND | No | Set to exactly 1 or true to enable the send tools. Any other value, or unset, leaves them off. | |
| GATEWAY_CHANNEL_ID | Yes | The channel ID the token belongs to. |
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 |
|---|---|
| channel_statusA | Read this channel's state from the gateway: whether the number is linked and connected. Set include_safety to also read the channel's health readings and overall verdict. |
| list_chatsA | List the chats the gateway has observed on this channel, from its own message log. This is not the account's full chat list: chats with no activity since the number was linked are absent. Returns up to 100 chats; the public API does not accept paging parameters. |
| read_messagesA | Read one conversation from this channel's message log, newest first: a person or a group. For a person, both of their WhatsApp addresses (phone number and LID) are read as one timeline where the channel holds the lid_lookup grant; |
| list_groupsA | List the WhatsApp groups this channel's number is in. This asks WhatsApp itself; do not poll it. A 429 whatsapp_rate_limited means WhatsApp is throttling the number: wait retry_after seconds. |
| get_groupA | Read one group: its subject, description, settings and participants. This asks WhatsApp itself; do not poll it. A 429 whatsapp_rate_limited means WhatsApp is throttling the number: wait retry_after seconds. |
| get_communityA | Read one community this channel's number belongs to. This asks WhatsApp itself; do not poll it. A 429 whatsapp_rate_limited means WhatsApp is throttling the number: wait retry_after seconds. |
| list_community_subgroupsA | List the groups linked to a community. This asks WhatsApp itself; do not poll it. A 429 whatsapp_rate_limited means WhatsApp is throttling the number: wait retry_after seconds. |
| get_contactA | Read this channel's stored entry for one contact (the names its contact store holds); this does not ask WhatsApp. |
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 8 tools
Each tool targets a distinct resource (channel status, chats, contacts, messages, groups, communities). The main potential confusion is list_chats (from the gateway's log) versus list_groups (queried from WhatsApp), but the descriptions explicitly spell out this log-vs-live distinction, so misselection risk is low.
Most tools follow a clean verb_noun pattern (list_chats, get_contact, read_messages, list_groups, get_group, get_community, list_community_subgroups). The lone deviation is channel_status (noun_state) and the minor read_ vs get_ split for retrieval, but the set is highly readable overall.
Eight tools is well-scoped for a WhatsApp gateway: channel health, chat/message reading, contacts, groups, and communities each earn their place without redundancy.
The surface is coherent but read-only: there is no send-message tool, no list_contacts (only get_contact), and no way to create or modify groups, which are obvious lifecycle gaps for a messaging-domain server. Core read workflows are covered, but agents will hit dead ends for any write action.