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: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.
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.
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:Use Authorization Bearer instead
Swap the header if your client prefers bearer auth:Cursor
Tools
Project MCP exposes grouped tools. Most tools accept anaction and params.
Use
action: "help" on grouped tools to list actions and see example payloads.
Examples
Ask your agent to check setup: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.