← Registry

API Tools

waloops.com

An MCP server for the WALoops OTP API that lets users send and verify one-time passwords, check usage limits, and list templates.

1 endpoint20 known toolsFirst detected November 3, 2026Last detected November 3, 2026

ENDPOINT 1

https://app.waloops.com/api/mcp.php

No auth detected

MCP server metadata

Name
waloops
Version
1.0.0
Capabilities
tools
Server instructions

Get a free key with the get_started tool. Free OTP key: OTP tools. Advance plan key: templates, inbox, stats, campaigns, and automation drafts. Available automation tools include list_connected_apps, list_actions, list_recipes, list_bot_flows, list_tags, create_automation_draft, and install_recipe_draft. Be creative: any trigger can be combined with any action and with conditions and delays — e.g. alert the team on WhatsApp for high-value orders, tag repeat customers, push orders to a sheet via webhook, start a bot flow after delivery. Propose ideas the merchant has not thought of. Everything you create is a safe draft the owner reviews and switches on in the app. OTPs work instantly from the WALoops number with no WhatsApp or Meta setup.

Known tools 20

get_started

Explain WALoops setup, key types, available tool groups, API docs, and example OTP requests.

Inferred read-only
send_otp

Send an OTP to an international phone number.

Potential side effects
verify_otp

Verify a previously sent OTP using the recipient’s phone number and code.

Inferred read-only
get_otp_usage

Read OTP usage for the API key, including available usage or limits.

Inferred read-only
list_templates

Requires an Advance plan key.

Inferred read-only
send_template

Requires an Advance plan key.

Inferred read-only
get_dashboard_stats

Requires an Advance plan key.

Inferred read-only
list_conversations

Requires an Advance plan key.

Inferred read-only
get_conversation_messages

Requires an Advance plan key.

Inferred read-only
list_automations

Requires an Advance plan key.

Inferred read-only
list_connected_apps

Requires an Advance plan key.

Inferred read-only
list_actions

Every action an automation can run (WhatsApp, Shopify, WooCommerce, webhook to any external tool, bot flows, tags) with the action_config each needs.

Inferred read-only
list_recipes

Requires an Advance plan key.

Inferred read-only
list_bot_flows

Requires an Advance plan key.

Inferred read-only
list_tags

Requires an Advance plan key.

Inferred read-only
install_recipe_draft

Requires an Advance plan key.

Inferred read-only
list_campaigns

Requires an Advance plan key.

Inferred read-only
create_template

Requires an Advance plan key.

Inferred read-only
pause_automation

Requires an Advance plan key.

Inferred read-only
create_automation_draft

Requires an Advance plan key.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.waloops]
url = "https://app.waloops.com/api/mcp.php"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "waloops": {
      "type": "http",
      "url": "https://app.waloops.com/api/mcp.php"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: waloops
Remote MCP URL: https://app.waloops.com/api/mcp.php

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "waloops": {
      "url": "https://app.waloops.com/api/mcp.php"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "waloops": {
      "type": "http",
      "url": "https://app.waloops.com/api/mcp.php"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "waloops",
  "transport": "streamable-http",
  "url": "https://app.waloops.com/api/mcp.php"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.