ENLAZÁ · WHATSAPP BUSINESS WITH AI
Developers · MCP
WhatsApp Business over MCP. Straight to your agent.
Use Enlazá’s remote MCP server to give your agent WhatsApp Business tools. One HTTPS endpoint, per-user authentication, and reading, sending and event capabilities governed by granted permissions.
MCP means Model Context Protocol: an interface for clients to discover and run tools. Enlazá hosts the connection; adding this endpoint requires no local bridge, Docker or npm package. Your application remains responsible for the agent’s behaviour.
The connection, in practice
Server URL: https://enlaza.chat/mcp
Transport: Remote HTTPS · HTTP POST
Authentication: OAuth + PKCE S256
Alternative: personal Bearer token
Read: whatsapp:read
Send: whatsapp:send
Events: whatsapp:events + whatsapp:readThe client discovers available tools after authorization. Granted permissions can change which tools are exposed.
Three ways to get started
Turn a conversation into useful work.
Illustrative examples for conversations you have authorized. These are not customer results.
Retrieve conversation context
Build a bounded conversation-reading workflow that summarizes decisions without mixing numbers or assuming complete history.
What you get: Paginated context for the selected number. Follow the cursor when the task needs more results and check history availability.
Discover the tools and call whatsapp_accounts. Use the full authorized number id to read one page of whatsapp_messages and suggest three actions.
Handle message media
Messages include reply and reaction context. Request media for visual content; available voice-note transcripts arrive as text.
What you get: An agent that distinguishes text, transcripts and actual visual content. Display capabilities depend on the host.
Read the requested message. For a photo, use whatsapp_media. For a supported voice note, check its available transcript before requesting another operation.
Build verifiable sending
Separate preparation, authorization, acceptance and delivery. Retain the operation identifier to reconcile uncertain outcomes.
What you get: A workflow with idempotent retries and explicit states, subject to permissions and messaging rules.
For this authorized recipient and content, use the available sending tool. Retain request_id and check whatsapp_message_status before claiming delivery.
From an idea to your first task
- Configure the remote endpoint in your MCP client. Use OAuth when available: PKCE S256, metadata discovery and dynamic client registration.
- Choose minimal scopes: whatsapp:read, whatsapp:send when needed, and whatsapp:events with read for events. Personal tokens are an alternative for clients with secure credential storage.
- Initialize and discover the actual tool catalogue. Check whatsapp_accounts and whatsapp_connection_check, then execute the authorized task. Do not infer tools from a product name.
Choose the workflow you need
Choose MCP when your application already supports tools and per-user authorization. If you need a campaign engine, contact centre or orchestrator, evaluate those components separately. To choose the best WhatsApp MCP server for your project, check real message access, media, account isolation, retries and your client’s event support.
Common questions
How do notifications work?
The client needs MCP Events support in addition to ordinary tools. Check subscription and permissions with whatsapp_notifications_status. A tool connection does not imply an active event subscription; retain checkpoints and deduplicate events when catching up.
What are the writing limits?
Text and images require a 24-hour window after a real incoming message from the recipient. Templates must be approved, eligible and covered by opt-in and authorization. Marking read requires write permission. Reading reactions does not imply sending them.
Where is the full contract?
At /agents.md: discovery, OAuth, tokens, tools, media, pagination and recovery. Keep tokens out of URLs and conversations; use the client’s secure credential field. The assistant follows its host’s approval requirements.