MCP server

Let AI agents operate your WhatsApp numbers through MCP.

Documentation Index

Fetch the complete documentation index at: https://docs.wazapin.id/llms.txt Use this file to discover all available pages before exploring further.

Project MCP gives AI agents live tools to send messages, read conversations, manage templates, and configure webhooks on your WhatsApp numbers.

Use it when an MCP-capable agent should operate a WhatsApp number without shell access — read inbound messages, send replies, manage templates, configure webhooks, and inspect channels.

Endpoint:

https://api.wazapin.com/mcp

Discovery (no auth): GET https://api.wazapin.com/.well-known/wazapin-mcp.json — tool names, actions, and auth headers.

API key scopes (MCP)

Optional JSON scopes on the API key restrict MCP tools:

Empty scopes = no MCP restriction (full access still limited by Casbin on REST).

Authentication

Choose the auth option your MCP client supports:

• API key (recommended): create an organization API key in the dashboard and pass it as a header. The key must start with wzp_. Organization context is inferred from the key.
• Session bearer: use a dashboard session token as Authorization: Bearer … when your client already has a logged-in session with an active organization.

Both options expose the same Project MCP tools when the caller is authorized.

Accepted API key headers:

Authorization: Bearer YOUR_API_KEY

X-Api-Key: YOUR_API_KEY

Use Authorization: Bearer for bearer-token clients. Use X-Api-Key when your MCP client lets you configure custom headers.

Connect

API key

Set your API key:

export WAZAPIN_API_KEY="wzp_your_key"

claude mcp add --transport http wazapin https://api.wazapin.com/mcp \
  --header "X-Api-Key: $WAZAPIN_API_KEY"

{
  "mcpServers": {
    "wazapin": {
      "url": "https://api.wazapin.com/mcp",
      "headers": {
        "X-Api-Key": "${env:WAZAPIN_API_KEY}"
      }
    }
  }
}

{
  "mcpServers": {
    "wazapin": {
      "url": "https://api.wazapin.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:WAZAPIN_API_KEY}"
      }
    }
  }
}

Use Authorization Bearer instead

Swap the header if your client prefers bearer auth:

{
  "mcpServers": {
    "wazapin": {
      "url": "https://api.wazapin.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:WAZAPIN_API_KEY}"
      }
    }
  }
}

Tools

Project MCP exposes grouped tools. Most tools accept an action and params.

Use action: "help" on grouped tools to list actions and see example payloads.

Examples

Ask your agent to check setup:

Use the wazapin MCP server to check my project status and tell me the next action.

Ask your agent to read and send WhatsApp messages:

Use wazapin conversations with action=list to list recent open conversations, then messages with action=list for the latest thread.

Use wazapin messages with action=send to send "Hello from Wazapin" to +6281234567890 from my connected channel.

Configure outbound webhooks:

Use wazapin webhooks with action=list, then explain which event types I can subscribe to.

Project MCP vs docs

Use the REST API or TypeScript SDK when your agent has HTTP or code access. Use Project MCP when your agent supports MCP and should call Wazapin tools directly.