WhatsApp MCP platform for AI agents

You control WhatsApp. Your AI agents get useful tools.

WAMCP pairs a real WhatsApp session once, exposes a production REST API and Streamable HTTP MCP endpoint, and lets the owner decide exactly what each agent can read, send, provision, and audit.

ClaudeCursorGrokCodexCustom MCP clients
WAMCP agent workspace showing WhatsApp-style chats, agent permissions, MCP connections, sync health, and audit timeline.
33

MCP tools for messaging, sync, notifications, and lifecycle

4

MCP resources for session, sync, unread notifications, and messages

60s

typical QR or phone-code pairing flow

3 keys

tenant, REST API, and MCP credentials stay scoped

For humans

A friendly control layer for the WhatsApp account owner.

The owner does not need to think in protocols. They pair WhatsApp, name the agents, choose permissions, and watch health and audit activity in one focused portal.

Give every agent a named identity

Create separate access for Claude, Cursor, Grok, Codex, or your own framework. Each one gets clear permissions and can be revoked without touching the rest.

Control read, send, and provision rights

Keep casual assistants read-only, allow trusted workflows to send replies, and reserve provisioning for owner-approved automation.

Build reactive WhatsApp loops

Use notification watching, chat retrieval, recipient resolution, quoted replies, reactions, media download, and audit checks as real production sequences.

For AI agents

Clear protocol surface. Concrete tool names. Machine-readable product facts.

Agents can discover what WAMCP is, how to connect, which credentials to use, and which actions are available without guessing from marketing copy.

Agent-readable summary
ProductWAMCP is a WhatsApp MCP platform and REST API for AI agents.
EndpointStreamable HTTP MCP is available at POST /mcp with bearer mcp tokens.
Tools33 MCP tools cover messaging, chats, contacts, groups, sync, health, notifications, lifecycle, and audit.
Credentialstnt tenant keys start connect flows, wbot keys call REST, and mcp bearer tokens authorize agents.
ControlsOwners can grant read, send, and provision permissions per agent and revoke access anytime.
POST https://wamcp.app/mcp
Authorization: Bearer mcp_...
MCP-Protocol-Version: 2025-11-25
Accept: application/json, text/event-stream

Platform

Built for real WhatsApp automation, not demo chatbots.

WAMCP connects the Whatsmeow bridge, Supabase Postgres, Realtime events, Cloudflare R2 media, REST endpoints, and MCP tools into one product surface.

WhatsApp-style pairing

Start with QR or an 8-digit phone-code flow, then poll connect status until the session is online and ready.

REST plus Streamable HTTP MCP

Use REST for tenant onboarding and direct API work, then let agents call the standard MCP endpoint at /mcp.

Sync-aware sessions

Agents can wait for sync, inspect health, reconnect sessions, and avoid acting while WhatsApp history is still protected.

Multi-tenant isolation

Tenant keys, session API keys, and MCP tokens isolate partners, users, sessions, audit data, and permissions.

Owner portal

The account owner gets a minimal PWA for agent access, portal sign-in, passkeys, alerts, and session control.

Reliable bridge

Built on a Go Whatsmeow backend with Supabase Postgres, Realtime events, and Cloudflare R2 media storage.

How it works

Pair once. Give agents scoped access. Keep the owner in charge.

  1. 1Pair WhatsApp with /connect, QR, or phone code.
  2. 2Receive scoped wbot and mcp credentials after connect success.
  3. 3Paste the MCP block into Claude, Cursor, Grok, Codex, or your agent host.
  4. 4Use skills for triage, digests, memory recall, group coordination, and reactive replies.
  5. 5Review health, permissions, notifications, and audit history from the owner portal.

Scoped credentials

Tenant keys start pairing, REST API keys manage one session, and MCP bearer tokens bind agent calls to a specific WhatsApp account.

Self-chat confirmation

Sensitive handoff and owner flows can require confirmation from the account owner's own WhatsApp self-chat.

Audit transparency

Agent actions, MCP activity, invalid auth, tenant boundaries, and operational status are inspectable instead of hidden in a black box.

Ready to connect WhatsApp to your agents?

Start with the live connect flow, then use the portal and production skills to keep the system understandable for people and reliable for AI.