WALoops MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WALOOPS_API_KEY | No | Optional WALoops API key (sent as X-API-Key). Not needed for initialization, tool listing or get_started; required for tools that send or read account data. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_startedA | Explain WALoops setup, key types, available tool groups, API docs, and example OTP requests. |
| send_otpB | Send an OTP to an international phone number. A free OTP key sends from the WALoops WhatsApp number; channel may be whatsapp or sms. |
| verify_otpB | Verify a previously sent OTP using the recipient’s phone number and code. |
| get_otp_usageB | Read OTP usage for the API key, including available usage or limits. |
| list_templatesA | Requires an Advance plan key. List the client’s approved WhatsApp templates and their variables. |
| send_templateA | Requires an Advance plan key. Send an approved WhatsApp template; call list_templates first to confirm the template name and variables. |
| get_dashboard_statsB | Requires an Advance plan key. Messages, conversations, automations and plan usage overview. |
| list_conversationsB | Requires an Advance plan key. List and search inbox conversations. |
| get_conversation_messagesB | Requires an Advance plan key. List messages in a conversation. |
| list_automationsA | Requires an Advance plan key. List automations, or fetch one automation with its run stats by id. |
| list_connected_appsA | Requires an Advance plan key. Connected apps (Shopify, WooCommerce, etc.) with their app_key and available event_key triggers; call before create_automation_draft. |
| list_actionsA | Every action an automation can run (WhatsApp, Shopify, WooCommerce, webhook to any external tool, bot flows, tags) with the action_config each needs. Combine any trigger from list_connected_apps with any action. |
| list_recipesA | Requires an Advance plan key. List proven ready-made automations that can be installed as safe drafts. |
| list_bot_flowsB | Requires an Advance plan key. List bot flows available as automation actions. |
| list_tagsA | Requires an Advance plan key. List tags available as automation actions. |
| install_recipe_draftA | Requires an Advance plan key. Installs a recipe as a switched-off draft for the owner to review. |
| list_campaignsA | Requires an Advance plan key. List campaigns, or fetch one campaign by id. |
| create_templateA | Requires an Advance plan key. Creates a WhatsApp template and submits it to Meta for approval (usually minutes to a few hours). Check status later with list_templates. |
| pause_automationA | Requires an Advance plan key. Switches an automation OFF. For safety, automations can only be turned ON by the account owner inside the WALoops app. |
| create_automation_draftB | Requires an Advance plan key. Creates an automation as a DRAFT: saved switched OFF and named "[AI draft] ...". Nothing is sent until the account owner reviews it and turns it on in the WALoops app (Automations page). Tell the user this. |
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 20 tools
Most tools target clearly distinct resources and actions, and descriptions distinguish e.g. custom automation drafts from recipe drafts. There is some overlap among the automation-building reference tools, especially list_actions versus list_bot_flows/list_tags, but not enough to cause serious misselection.
Tool names consistently use snake_case with a predictable verb_noun or verb_noun_detail structure. Deviations like get_started are minor and do not break the overall pattern.
Twenty tools is somewhat heavy, but the server spans several distinct areas: OTP, templates, campaigns, conversations, dashboard, and automations. Each tool has a plausible role, though the automation reference tools could likely be consolidated.
Core OTP and safe automation-draft workflows are well covered, but there are notable gaps: campaigns are list-only, templates lack update/delete, and conversations lack a reply/send-message operation. These gaps may force the agent to fall back to the WALoops app for common lifecycle actions.