WhatsApp MCP Service

Model:

Connect WhatsApp to your MCP server

Starting WhatsApp Service

Please wait while we initialize...

Multi-clinic onboarding — each registry row below is its own Puppeteer isolate + QR scan. The large QR above is the legacy single session (WHATSAPP_SESSION_NAME). New clinics: use the onboarding link from your dashboard (opaque token in the URL) — clinic staff do not enter tenant identifiers. The WhatsApp MCP service derives the clinic binding server-side before Agnentic writes whatsapp_agent_sessions after you scan QR.

Verify onboarding JWT (signature + expiry + clinic id)

Runs on this server using WHATSAPP_ONBOARDING_JWT_SECRET. Use before sharing a link or when debugging dashboard mint output.

Open the WhatsApp pairing button or link after clinic setup (dashboard mints an opaque token). On this page URL it looks like ?onboarding=<jwt>.

Registry sessions

No registry sessions yet. Continue from your clinic onboarding link, or expand dev tools if enabled.

Binding still runs only after WhatsApp reaches ready + Agnentic bind-session.

Service Information

Next.js Service: localhost:3002

MCP Server: mcp-proxy --port 8084 -- python server.py