[Purpose] Gambot MCP wraps the official WhatsApp Business (Cloud) API as a Model Context Protocol (MCP) server and REST API for AI agents, enabling AI clients such as Claude, Cursor, Codex, Gemini CLI, VS Code/Copilot, and Windsurf to send WhatsApp messages and templates and to manage CRM, leads, and marketing campaigns. Official materials state that Gambot is a Meta-authorized Business Solution Provider (BSP) that uses the official API rather than WhatsApp Web automation, so no QR code, linked personal session, or headless browser is required, and it supports real business accounts, approved templates, and Meta-supported delivery.
[Main Capabilities]
- Send WhatsApp messages and approved templates; provides runnable examples (Node/TypeScript, Python, Next.js, Laravel/PHP) for sending messages, sending templates, receiving webhooks, and delivery status.
- CRM-related management: contacts, leads, cases, tasks, quotes, invoices, orders, and marketing campaigns.
- Bots and automation: a conversation bot typically consists of a set of botomations sharing a sourceFlowId, which in order includes the main bot (in three forms: menu / ai / combined), an activator, and human_intervention_cancel.
- Agent behavior support: structured errors include fields such as error_code, reason, can_recover, recommended_action, required_tool, relevant_contact, and template_required; built-in 24-hour customer service window and template guidance; provides the unified entry-point tool gambot_setup_whatsapp_integration.
- Tool annotations: read-type tools are marked as read-only/idempotent; delete_*, disable_user, and issue_invoice are marked as destructive; all tools are openWorld.
- Account creation: no API key is required; the agent can create a Gambot account on its own; the only manual step is completing the Meta WhatsApp connection in the browser.
[How to Use] Run locally: npx -y gambot-mcp (no cloning or building required; the MCP client runs it on demand via npx). Hosted server:https://gambot-mcp.azurewebsites.net/mcp(Streamable HTTP, OAuth 2.0 or token). You can start without a token: when GAMBOT_TOKEN is not set, the server runs in bootstrap mode and creates an account. Existing accounts can use a Gambot Token (gmbt_…, located in Settings → General) as GAMBOT_TOKEN (local) or Authorization: Bearer gmbt_… (hosted/REST). Official guidance states that the token is confidential and must never be pasted into chats or placed under source control. You can use the environment variable GAMBOT_API_BASE to override the base URL (default https://api.gambot.co.il/api/v1)。
[Use Cases] Suitable for developers and teams that need to connect official WhatsApp business capabilities to AI agents, for example: sending customers order shipment notifications; using templates to send bulk promotions to tagged contacts; querying the day's message volume and number of pending replies; summarizing customer service conversations; scheduled marketing campaigns; building lead bots (sending a welcome template with buttons when ads generate leads, and stopping when human intervention occurs).
[Limitations and Notes] Official materials do not provide specific pricing, rates, or platform availability information, so none is currently provided. MCP is an AI interface to Gambot's public REST API, uses the same business logic as the REST API, and is not a separate backend. Gambot AI bots of the AI/combined type must be built in the Bot Builder app because Gambot AI configuration is required. When encountering CONVERSATION_WINDOW_CLOSED / TEMPLATE_REQUIRED, switch to sending a template; for MISSING_TEMPLATE_VARIABLES, first obtain the template variables; for CONTACT_NOT_FOUND, first look up the contact and do not guess the recipient; when encountering rate limits, back off, and for bulk sending, use marketing campaigns. Supported clients and corresponding setup guides are listed (Cursor, Claude, ChatGPT, Gemini).