EnoSend MCP running

Model Context Protocol endpoint for the EnoSend WhatsApp API. One hosted endpoint — every EnoSend customer authenticates with their own API key.

Endpoint

POST /mcp — JSON-RPC 2.0 over HTTPS.

Auth

Every request must include your EnoSend API key as a Bearer token:

Authorization: Bearer wa_live_…

Grab your key from the EnoSend dashboard → API Keys. The key identifies you — your sends land in your dashboard, billed against your wallet.

Claude Desktop / Claude Code

{
  "mcpServers": {
    "enosend": {
      "url": "https://mcp.enosend.com/mcp",
      "headers": { "Authorization": "Bearer wa_live_YOUR_KEY" }
    }
  }
}

Claude.ai custom connector (OAuth form)

Same hosted URL, but the form wants OAuth fields. Use a fixed Client ID and put your API key in Client Secret:

Remote MCP Server URL	`https://mcp.enosend.com/mcp`
OAuth Client ID	`enosend-mcp` (same for everyone)
Client Secret	`wa_live_YOUR_KEY` (your API key — different per account)

The Client ID is not your API key. Only the secret field carries wa_live_….

Tools exposed

list_instances — show your connected WhatsApp numbers
check_human_mode — inspect Human-mode state for an instance
toggle_human_mode — enable/disable Human-mode + change pace
send_message — send one WhatsApp text (returns immediately; no polling)
get_message_status / check_message_status — check if a message was delivered
send_bulk_messages — send to up to 500 recipients in one call
get_bulk_status — poll a bulk batch by campaign_id

REST docs: enosend.com/whatsapp/docs/