gambot-mcp
OfficialSummary: An MCP server that lets AI clients operate a Gambot official WhatsApp Business account for messaging, CRM, campaigns, billing documents, users, and onboarding.
Send WhatsApp free-text messages and approved templates with variables and media headers.
Read conversations and message history, list/inspect/create templates, and upload template media.
Manage contacts, leads, cases, and tasks with custom fields, tags, and notes.
Create/update quotes, invoices, orders, signatures, web forms, and document-template fill links; issue invoices.
Invite/list/get/update/enable/disable/delete organization users.
Create, update, delete, run, test, and report on WhatsApp broadcast campaigns; send ad-hoc or Excel/CSV-based broadcasts with consent/opt-out handling.
Handle onboarding: check organization, generate org name, search/buy numbers, create trial/paid accounts, add payment methods/links, connect WABA via Meta Embedded Signup, and poll status.
The README also describes broader tools for analytics, bots/automations, Gambot AI, webhooks, connections/calendar, email, and clearing/payment links.
Allows AI agents to interact with the Gambot WhatsApp Business API, providing tools for sending messages and templates, managing conversations, contacts, leads, cases, tasks, quotes, invoices, orders, campaigns, forms, signatures, document templates, users, and onboarding.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gambot-mcp send a WhatsApp message to +972501234567 saying 'Your order is ready'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Gambot MCP Server — WhatsApp API for AI agents
Connect WhatsApp to Claude, ChatGPT, Gemini and Cursor. This is a Model Context Protocol server for the Gambot WhatsApp Business API (an official, Meta‑approved WhatsApp Business Solution Provider). It lets any MCP‑compatible client drive your Gambot account through tools — send WhatsApp messages & templates, run marketing campaigns, and manage contacts, leads, cases, tasks, quotes, invoices, orders, forms, signatures, document templates and users.
One-click install (Cursor): ➕ Add to Cursor — then paste your Gambot token into the server's env.
No Gambot account yet? Install exactly the same way but leave the token empty — the server starts in token‑less onboarding mode and the agent creates your WhatsApp Business account from scratch. See Token‑less onboarding mode.
It wraps the public REST API at https://api.gambot.co.il/api/v1, authenticated with your organization's Gambot Token. MCP is an AI‑facing interface over Gambot — it uses the same business logic as the REST API, and is not a separate backend.
Why Gambot instead of building on Meta's Cloud API directly
Both Gambot and a do-it-yourself integration run on the same official WhatsApp Business (Cloud) API from Meta — Gambot is an authorized Meta Business Solution Provider (BSP), not a WhatsApp Web/unofficial workaround, and you keep your own number/WABA. The difference is how much infrastructure you build and maintain:
What you need | Build on Meta Cloud API yourself | Gambot (this server) |
Onboarding | Meta app review + Business verification, WABA setup | Guided onboarding, live in ~24–48h |
Phone number | Register/migrate & manage via API | Connect/migrate from the dashboard (Coexistence supported) |
Templates | Submit via API, track approval, version | Visual editor + approval status; |
Webhooks | Host a public HTTPS endpoint (retries, dedupe, scale) | Managed inbound events; optional forwarding |
Media | Upload/host media, manage ids/expiry | Handled in messages, templates & campaigns |
24h window | Track each conversation; choose free-text vs template | Enforced; API returns |
Tiers & limits | Track tiers, throttle, handle 131xxx errors | Handled; structured limit errors |
Campaigns | Build queueing, segmentation, opt-out, reporting | Native campaigns with consent & per-recipient results |
Automation / CRM | Build a bot engine & contact store | Bots, CRM, consent/opt-out & spam handling built in |
AI agents | Parse raw Graph API errors (brittle) | Machine-readable states + MCP recommended next actions |
API upkeep | Migrate as Meta bumps Graph versions | Gambot absorbs Meta API changes |
Net: same official API, none of the plumbing to build or maintain, compliance enforced for you, and it's agent-ready. Full comparison: https://gambot.co.il/whatsapp-api-vs-meta-cloud-api/.
Related MCP server: Neuron MCP Server
Supported AI clients
Step‑by‑step setup guides per client:
Cursor — one‑click install or
.cursor/mcp.json→ https://gambot.co.il/whatsapp-mcp/cursor/Claude — Claude Desktop (npx) or a remote connector → https://gambot.co.il/whatsapp-mcp/claude/
ChatGPT — hosted connector (Streamable HTTP + OAuth) → https://gambot.co.il/whatsapp-mcp/chatgpt/
Gemini — Gemini CLI settings → https://gambot.co.il/whatsapp-mcp/gemini/
Hosted (remote) server: https://mcp.gambot.co.il/mcp (Streamable HTTP; OAuth or bearer token) — no local install needed.
Prerequisites
Node.js 18+
No account yet? You need nothing — start the server without a token and it runs in token‑less onboarding mode to create your Gambot account from scratch.
Already have an account? A Gambot Token (
gmbt_…) from the Gambot admin panel → Settings → General, to unlock the full tool set.
Quick start (npx — recommended)
Once published to npm, no clone or build is needed — MCP clients run it on demand with npx.
Cursor (.cursor/mcp.json) / Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"gambot": {
"command": "npx",
"args": ["-y", "gambot-mcp"],
"env": {
"GAMBOT_TOKEN": "gmbt_your_token_here"
}
}
}
}Optional env var GAMBOT_API_BASE overrides the base URL (defaults to https://api.gambot.co.il/api/v1).
No token yet? Token‑less onboarding mode
You don't need a Gambot account to get started. The token is a result of finishing onboarding (chicken‑and‑egg: a brand‑new org has no token yet), so the server also runs without GAMBOT_TOKEN. Just omit it — leave env empty:
{
"mcpServers": {
"gambot": {
"command": "npx",
"args": ["-y", "gambot-mcp"]
}
}
}Started token‑less, it enters onboarding mode and exposes only the public self‑serve tools — create a brand‑new account (free / co‑existence / bring‑your‑own number, or buy a number after e‑mail+WhatsApp verification), open the Meta Embedded Signup link in the browser, then poll gambot_get_onboarding_status until WhatsApp is connected. Just tell the agent "create a Gambot WhatsApp account for my business" and it walks you through it. Once connected, you get your gmbt_… token in‑app (Settings → General); add GAMBOT_TOKEN to the env above to unlock the full tool set. (Remote/OAuth clients like Claude & ChatGPT authorize per‑session through the hosted consent page instead.)
Local development (from source)
npm install
npm run buildThen point your MCP client at the built entrypoint:
{
"mcpServers": {
"gambot": {
"command": "node",
"args": ["C:/Users/you/source/repos/gambot/gmbt_mcp/dist/index.js"],
"env": {
"GAMBOT_TOKEN": "gmbt_your_token_here"
}
}
}
}Tools
Group | Tools |
Messages |
|
Conversations |
|
Templates |
|
Contacts |
|
Leads |
|
Cases |
|
Tasks |
|
Notes |
|
Analytics / reports |
|
Quotes |
|
Invoices |
|
Orders |
|
Payments / transactions |
|
Signatures |
|
Web forms |
|
Document templates |
|
Users |
|
Campaigns |
|
Bots & automations |
|
Gambot AI (brain) |
|
Onboarding |
|
Webhooks |
|
Connections |
|
| |
Clearing (סליקה) |
|
Calendar |
|
Facebook Lead Ads |
|
Bots & automations model
A conversational bot in Gambot is usually a package of botomations that were deployed together and share a sourceFlowId. gambot_list_bots returns role, triggerKind, sourceFlowId and linkedBotomationId on every item so an agent can reconstruct it. The full package, in order, is:
Main bot (
role: main_bot,isBot: true) — the conversation itself. Three flavours:menu — an opening template whose quick-reply buttons route to replies.
ai — a
GambotAistep that hands the conversation to Gambot AI (the AI operator).combined — a menu where some branches route to Gambot AI.
Activator / מפעיל (
role: activator) — the trigger that starts the bot.triggerKindtells you how it fires:incoming_message(keyword/any),template_button,campaign_lead(a lead arrived from an ad/campaign),owner_assigned(a contact was assigned to an owner — e.g. Gambot AI),scheduled, or inactivity re-engagement ("no message in X days").Human-intervention cancel / ביטול בוט בהתערבות אנושית (
role: human_intervention_cancel) — fires when a human agent sends a message and stops the running bot so it never talks over a human. One is seeded active per org; a package can deploy its own.
Gambot AI (the AI operator) = ownership. To route a contact to Gambot AI, assign the contact's owner to Gambot AI. The Gambot-AI botomation's trigger is contactOwner == the Gambot AI user, so it then answers with a GambotAi step. An activator can therefore do "if no communication in X days → assign the contact to Gambot AI", and the AI takes over.
Building a bot in one call. gambot_deploy_bot_package assembles the whole package for you, in order — (1) main bot, (2) activator, (3) human-intervention cancel — all sharing one sourceFlowId. Pick botType: "menu" (give openingTemplateName + options, and an activator that sends the opening template: keyword / any_message / inactivity / campaign_lead) or botType: "keyword" (self-activating — its keyword IS the activator, so no separate activator is created). AI/combined bots (Gambot AI) are built in the Bot Builder app because they need a Gambot AI configuration.
Turning a bot on/off: gambot_set_bot_status toggles one botomation; pass includePackage: true to turn the whole bot (main + activator + cancel + Gambot AI) on or off together. Use gambot_get_bot_package first to see exactly what will change.
Example prompts
"Send a WhatsApp to +972 50‑123‑4567 saying their order shipped."
"Message everyone tagged
VIPwith thepromo_launchtemplate.""How many WhatsApp messages did we receive today, and how many are waiting for a reply?"
"Summarize today's customer‑service conversations."
"Schedule a campaign to the
newslettertag for tomorrow at 10:00.""Build a lead bot: when a lead arrives from an ad, send the
welcome_leadtemplate with buttons Sales/Support, and stop if I jump in." →gambot_deploy_bot_package(botType: "menu", openingTemplateName: "welcome_lead", options: [...], activator: { type: "campaign_lead" })."Turn off my lead bot completely (the bot, its trigger and the AI answer)." →
gambot_get_bot_packagethengambot_set_bot_status(includePackage: true, status: "inactive")."Which bots are active, and what triggers each one?" →
gambot_list_bots(readrole+triggerKind).
Agent behavior, errors & recovery
Gambot MCP is designed so an AI agent can understand what happened and what to do next — it interprets the API's structured business state and returns actionable guidance.
Structured errors. On an API error the tool result is JSON with a stable machine‑readable
code, the humanmessage, the API'sdata(state flags), and — when recoverable — arecommendedActionnaming a real tool. Example:{ "status": "action_required", "code": "CONVERSATION_WINDOW_CLOSED", "message": "A free-form WhatsApp message cannot currently be sent.", "data": { "canSendFreeText": false, "canSendTemplate": true }, "recommendedAction": { "tool": "gambot_send_template", "reason": "The 24-hour window is closed; send an approved template. List options with gambot_list_templates." } }Common recoveries.
CONVERSATION_WINDOW_CLOSED/TEMPLATE_REQUIRED→gambot_send_template;MISSING_TEMPLATE_VARIABLES→gambot_get_template_variables(then ask the user);CONTACT_NOT_FOUND→gambot_list_contacts(never guess a recipient);RATE_LIMITED/ messaging‑limit → back off, don't loop, use a campaign for bulk.Safety. The agent never silently picks an ambiguous recipient, and never loops single‑send tools for bulk — it's routed to campaigns.
Tool annotations. Read tools are marked read‑only/idempotent;
delete_*,disable_userandissue_invoiceare marked destructive; every tool isopenWorld(it talks to the live WhatsApp/Gambot backend). Use these to gate confirmations for external‑communication and high‑impact actions.
REST API & docs
REST reference, auth, scopes and the full error‑code vocabulary: https://gambot.co.il/developers/
WhatsApp API for AI agents: https://gambot.co.il/whatsapp-api-for-ai-agents/
Security
The Gambot Token is a secret (like a password). Keep it out of source control (use the client's env). You can rotate it any time from Gambot Settings → General, and optionally narrow its scopes there.
Publishing (maintainers)
This package ships with a server.json manifest for the official MCP Registry (registry.modelcontextprotocol.io). The registry only stores metadata, so the npm package must be published first, and the reverse‑DNS name in server.json must match mcpName in package.json (io.github.gambot-ai/gambot-mcp).
# 1) Publish the npm package (public)
npm publish --access public
# 2) Install the registry publisher CLI
# (see https://modelcontextprotocol.io/registry/quickstart)
brew install mcp-publisher # or download from the registry releases
# 3) Authenticate under the io.github.gambot-ai/* namespace and publish
mcp-publisher login github
mcp-publisher publishIf your GitHub owner is not
gambot-ai, update thenameinserver.json,mcpNameinpackage.json, and therepository/identifierfields to match before publishing.
Once listed in the official registry, aggregators such as Glama, PulseMCP and Smithery
index the server automatically. A smithery.yaml is also included for Smithery.
Available Tools
78 toolsgambot_add_payment_methodAdd payment method (card on file)A
Verify a card with the clearing provider (Tranzila) and save its token to an organization, so an AI agent with the customer's card can put a payment method on file without the hosted page. The raw card is sent only to the PCI-compliant clearing provider and never stored. For a hosted alternative (customer types the card), use gambot_create_payment_link.
Inputs: card (required), organizationName (required), plan.
gambot_check_organizationCheck organization (onboarding)B
Check whether an organization already exists for a company + tax id (ח.פ/ת.ז), and whether an incomplete onboarding can be resumed. Use before creating a new trial.
Inputs: companyName (required), companyIdNumber (required).
gambot_create_campaignCreate campaignA
Create a WhatsApp broadcast campaign. Manual (run on demand) or scheduled (one-time / recurring). For a template broadcast set messageType='Template' + wabaTemplateId; for free text set messageType='regular' + message. Audience: recipientSource='Excel' + ExcelData, or ContactFilters (CRM segment), or legacy ContactsQuery. Scheduling: campaignTrigger='Scheduled' + scheduleType ('once' with runAt+timezone, or 'repeated' with interval/intervalNumber/endCondition).
Inputs: messageType (required), campaignName (required), runAt, message, +13 more.
gambot_create_caseCreate caseC
Create a case (support ticket / פנייה). Accepts base fields plus a nested 'customFields' object.
Inputs: subject (required), stageId, category, priority, +5 more.
gambot_create_contactCreate contactA
Create a contact (returns the existing one if the phone is already known). Custom/dynamic fields go under 'customFields' (see gambot_get_contact_fields for keys).
Inputs: phoneNumber (required), keys, name, email, +2 more.
gambot_create_document_linkCreate document template fill linkA
Generate a distributable fill link for a document template. A template has no single static link (each customer fills their own copy), so this creates a fill-only instance and returns its public /form/ URL to share with the customer. Optionally pre-fill variables via contactPhone/leadId/variables.
Inputs: templateId (required), leadId, language, variables, +3 more.
gambot_create_invoiceCreate invoiceB
Create an invoice draft. invoiceData holds the invoice fields.
Inputs: invoiceData (required).
gambot_create_leadCreate leadA
Create a CRM lead (contact created if missing, optional template send). Accepts all base lead fields plus a nested 'customFields' object. See gambot_get_lead_fields for available fields.
Inputs: phoneNumber (required), keys, name, tags, +13 more.
gambot_create_orderCreate orderC
Create a store order. Body holds order fields (customer, items, total…).
Inputs: order (required).
gambot_create_paid_accountCreate paid account (no trial, card required)A
Create a new organization that goes STRAIGHT TO PAID — no free trial month. A payment method is MANDATORY: pass a card object; the card is verified with the clearing provider, its token is saved, and billing starts immediately (first charge on the next billing run). Use this when an AI agent has the customer's card and should provision a paying account in one call. Same number options and the same graceful companyInfo.timezone/country handling as gambot_create_trial_account (neither hard-fails). The raw card is sent only to the PCI-compliant clearing provider and never stored.
Inputs: card (required), companyInfo (required), plan, payEach, +5 more.
gambot_create_payment_linkCreate payment linkA
Build a secure hosted payment link (Tranzila) to add a card for an organization. Card data is never handled by the API — share the URL with the customer; the card token is saved on success.
Inputs: organizationName (required), plan, price, hasSim, +7 more.
gambot_create_quoteCreate quoteC
Create a price quote. quoteData holds the quote fields (title, items, total, contact…).
Inputs: quoteData (required).
gambot_create_taskCreate taskC
Create a task (optionally linked to a contact via contactPhone).
Inputs: title (required), dueDate, priority, description, +1 more.
gambot_create_templateCreate templateA
Create a new WhatsApp template (submitted to Meta for approval). Name must be English, lowercase_with_underscores. Components use the full Meta shape and support: a TEXT or media (IMAGE/VIDEO/DOCUMENT) HEADER, a BODY with {{1}} variables, a FOOTER, and BUTTONS (QUICK_REPLY / URL / PHONE_NUMBER). For a media header you can either put example.header_handle on the HEADER component yourself (upload it first with gambot_upload_template_media), or simply pass headerMediaUrl (a public URL) and let Gambot upload it and inject the handle.
Inputs: name (required), category (required), language (required), components (required), +3 more.
gambot_create_trial_accountCreate trial accountA
Create a new FREE-TRIAL organization + first user (no card required). Login credentials (temp password) are emailed & WhatsApp'd to the contact. WhatsApp/number options: useFreeNumber (Meta test number) · useCoexisting (existing WhatsApp Business number in simInfo.simNumberEntered) · BYO SIM (the customer's own number in simInfo.simNumberEntered) · Buy a SIM from us (simInfo.purchaseInTwilio=true + simInfo.selectedSimNumber from gambot_search_available_numbers). GLOBAL: send companyInfo.timezone (IANA) and companyInfo.country (ISO-3166 alpha-2) — they drive scheduling and locale. Neither hard-fails: a missing/invalid timezone is derived from country (else defaults to Asia/Jerusalem). For a paid account with a card on file (no trial) use gambot_create_paid_account instead. After creating, connect WhatsApp via the returned wabaConnectUrl or gambot_exchange_waba_token.
Inputs: companyInfo (required), plan, payEach, simInfo, +4 more.
gambot_create_userCreate (invite) userB
Create an organization user (team member). Sends a welcome email + WhatsApp invite.
Inputs: email (required), role, fullName, language, +4 more.
gambot_delete_campaignDelete campaignC
Delete a campaign by id.
Inputs: campaignId (required).
gambot_delete_userDelete userA
Permanently delete an organization user (removes both the auth account and the profile). This is irreversible — prefer gambot_disable_user to just deactivate access.
Inputs: userId (required).
gambot_disable_userDisable userC
Disable a user (status = inactive).
Inputs: userId (required).
gambot_enable_userEnable userB
Enable a user (status = active).
Inputs: userId (required).
gambot_exchange_waba_tokenExchange Meta code (connect WhatsApp)B
Complete Meta Embedded Signup by exchanging the authorization code returned by the Facebook popup. Registers the WABA, subscribes webhooks and registers the phone number.
Inputs: code (required), organization (required), wabaId, isCoexisting, +2 more.
gambot_generate_organization_nameGenerate organization nameB
Generate a unique organization name from a company name + tax id (adds a suffix if taken).
Inputs: companyName (required), companyIdNumber (required).
gambot_get_campaignGet campaignA
Get a single campaign by id.
Inputs: campaignId (required).
gambot_get_campaign_resultsGet campaign resultsB
Get the run results/report for a campaign (sent/delivered/read/replies/clicks).
Inputs: campaignId (required).
gambot_get_caseGet caseC
Get a single case by id.
Inputs: caseId (required).
gambot_get_case_fieldsGet case fieldsA
Get case (פנייה) field definitions: { baseFields, customFields }. Custom case values are stored under a nested 'customFields' map — pass them the same way on create/update.
Inputs: no named parameters.
gambot_get_contactGet contactA
Fetch a contact by phone number.
Inputs: phone (required).
gambot_get_contact_fieldsGet contact fieldsA
Get contact field definitions (base + custom/dynamic). Contacts store custom values as top-level keys — pass them via 'customFields' on create/update.
Inputs: no named parameters.
gambot_get_conversation_messagesGet conversation messagesC
Read the message history for a single conversation.
Inputs: phone (required), after, before, pageSize.
gambot_get_documentGet document templateC
Get a single document template.
Inputs: templateId (required).
gambot_get_document_submissionsGet document template submissionsC
Get fill-only submissions generated from a document template.
Inputs: templateId (required), limit.
gambot_get_formGet web formC
Get a single web form definition.
Inputs: formId (required).
gambot_get_form_linkGet web form public linkA
Get the stable public shareable link for a web form. Distribute it to customers via WhatsApp/email/SMS/QR; all submissions land in the form's submissions.
Inputs: formId (required).
gambot_get_form_submissionsGet web form submissionsB
Get submissions (results) for a web form.
Inputs: formId (required), limit.
gambot_get_invoiceGet invoiceB
Get a single invoice by id.
Inputs: invoiceId (required).
gambot_get_leadGet leadA
Get a single lead by id.
Inputs: leadId (required).
gambot_get_lead_fieldsGet lead fieldsA
Get lead field definitions: { baseFields, customFields }. Custom lead values are stored under a nested 'customFields' map — pass them the same way on create/update.
Inputs: no named parameters.
gambot_get_orderGet orderB
Get a single order by id.
Inputs: orderId (required).
gambot_get_quoteGet quoteC
Get a single quote by id.
Inputs: quoteId (required).
gambot_get_signatureGet signature documentB
Get a single e-signature document, including its signing results.
Inputs: documentId (required).
gambot_get_signature_linkGet signature signing linkA
Get the signing link(s) to distribute for an existing signature document (one per signer). Share with signers via WhatsApp/email/SMS.
Inputs: documentId (required).
gambot_get_taskGet taskA
Get a single task by id.
Inputs: taskId (required).
gambot_get_templateGet templateA
Get a single template by id, including Meta approval status.
Inputs: templateId (required).
gambot_get_template_variablesGet template variablesC
Get the dynamic variables of a template.
Inputs: templateId (required).
gambot_get_userGet userA
Get a single user by id.
Inputs: userId (required).
gambot_get_waba_connect_linkGet WhatsApp (WABA) connect linkA
Get the hosted page URL where the customer completes Meta Embedded Signup (the Facebook popup) to connect their WhatsApp Business account.
Inputs: organization (required).
gambot_issue_invoiceIssue invoiceB
Issue an invoice — locks it and assigns the official document number.
Inputs: invoiceId (required).
gambot_list_campaignsList campaignsB
List all broadcast campaigns for the organization.
Inputs: no named parameters.
gambot_list_casesList casesC
List cases (paginated).
Inputs: search, pageSize, pageNumber.
gambot_list_conversationsList conversationsC
List conversations (contacts) ordered by most recent message.
Inputs: search, pageSize, pageNumber.
gambot_list_documentsList document templatesC
List document templates.
Inputs: limit.
gambot_list_formsList web formsC
List web forms.
Inputs: limit.
gambot_list_invoicesList invoicesC
List invoices (paginated).
Inputs: type, search, status, pageSize, +1 more.
gambot_list_leadsList leadsC
List leads (paginated).
Inputs: search, pageSize, pageNumber.
gambot_list_ordersList ordersC
List orders (optionally filtered by status / store / date range).
Inputs: dateTo, status, storeId, dateFrom.
gambot_list_quotesList quotesC
List price quotes (paginated).
Inputs: search, status, pageSize, pageNumber.
gambot_list_scheduled_campaignsList scheduled campaignsA
List scheduled campaigns that are waiting to run.
Inputs: no named parameters.
gambot_list_signaturesList signature documentsB
List e-signature documents (newest first).
Inputs: limit.
gambot_list_tasksList tasksB
List tasks for the organization.
Inputs: no named parameters.
gambot_list_templatesList templatesA
List all WhatsApp templates for the organization.
Inputs: no named parameters.
gambot_list_usersList usersA
List organization users (excluding system bots).
Inputs: no named parameters.
gambot_run_campaignRun campaignA
Run an existing (saved) campaign by id now (resolves recipients and executes).
Inputs: campaignId (required).
gambot_search_available_numbersSearch phone numbers to buy (by country)A
List phone numbers available to purchase for a country (via Twilio), so you can pick one to buy as the account's SIM/number. Pass the chosen phoneNumber to gambot_create_trial_account / gambot_create_paid_account as simInfo.selectedSimNumber with simInfo.purchaseInTwilio=true.
Inputs: countryCode (required), numberType.
gambot_send_campaignSend ad-hoc campaignA
Run an ad-hoc campaign WITHOUT saving it first. Provide an audience (recipientPhoneNumbers, excelRecipients or filters) and the message (messageType='Template'+templateId, or 'regular'+message). Compliance is built in: every org has an ACTIVE opt-out flow (recipients reply הסר/stop/unsubscribe to be excluded from future broadcasts); the response echoes it under optOut (enabled=true) and your consent-to-mail under consent.
Inputs: messageType (required), filters, message, templateId, +5 more.
gambot_send_campaign_from_excelSend / schedule a template broadcast from an Excel/CSVA
Broadcast a WhatsApp TEMPLATE to everyone in an Excel/CSV the user gave you — the easiest way to do a mail-merge blast. YOU (the agent) read the sheet and pass: rows (one object per row, keyed by the column header), phoneColumn (which column holds the phone), and the variable mapping — either variableColumns (ordered: 1st column → {{1}}, 2nd → {{2}}, …) or variableMapping ({ var1:'ColName', var2:'ColName2' }). TIP: call gambot_get_template_variables first to see how many variables the template expects, then map columns to them. Sends immediately by default; to SCHEDULE add scheduling fields (scheduleType:'once' + runAt + timezone, or scheduleType:'repeated' + interval/intervalNumber/endCondition) — scheduled sends are saved as a campaign. Every original column is also stored per-recipient (rowData) so later automations can use any value by name. Compliance is built in: the org's ACTIVE opt-out flow (reply הסר/stop/unsubscribe) auto-excludes recipients from future broadcasts; the response echoes it under optOut (enabled=true) and your consent under consent.
Inputs: rows (required), phoneColumn (required), runAt, message, +13 more.
gambot_send_templateSend WhatsApp templateA
Send an approved WhatsApp template with variables. Can initiate a conversation even outside the 24-hour window.
Inputs: to (required), templateId (required), country, variables.
gambot_send_textSend WhatsApp textA
Send a free-text WhatsApp message. Only works inside the 24-hour customer service window; outside it, use gambot_send_template.
Inputs: to (required), text (required), country.
gambot_test_campaignTest campaign (single recipient)A
Send a single-recipient TEST of a template or free-text message. Great for previewing before a full broadcast.
Inputs: to (required), country, message, variables, +3 more.
gambot_update_campaignUpdate campaignB
Update a campaign (send the full campaign object).
Inputs: campaign (required), campaignId (required).
gambot_update_caseUpdate caseA
Update a case — only the provided fields are changed. Accepts base fields plus a nested 'customFields' object (merged with existing custom values).
Inputs: caseId (required), stageId, subject, category, +4 more.
gambot_update_contactUpdate contactA
Update a contact — only the provided fields are changed. Custom fields go under 'customFields'.
Inputs: phone (required), keys, name, email, +1 more.
gambot_update_invoiceUpdate invoiceB
Update invoice fields (blocked once issued/locked).
Inputs: fields (required), invoiceId (required).
gambot_update_leadUpdate leadA
Update a lead — only the provided fields are changed. Accepts any base field plus a nested 'customFields' object (merged with existing custom values).
Inputs: leadId (required), tags, notes, title, +5 more.
gambot_update_orderUpdate orderB
Update order fields (merge).
Inputs: fields (required), orderId (required).
gambot_update_quoteUpdate quoteC
Update quote fields (partial).
Inputs: fields (required), quoteId (required).
gambot_update_taskUpdate taskB
Update a task — only the provided fields are changed.
Inputs: taskId (required), title, status, dueDate, +4 more.
gambot_update_userUpdate userC
Update user fields — only the provided ones are changed.
Inputs: userId (required), role, email, status, +7 more.
gambot_upload_template_mediaUpload template mediaA
Upload a public media URL (image/video/document) to Meta and get a reusable header_handle for a template's media HEADER. Use the returned headerHandle inside a HEADER component: {type:'HEADER',format:'IMAGE',example:{header_handle:[headerHandle]}}.
Inputs: url (required), type.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 78 tools
Most tools are cleanly separated by resource and action, so an agent can usually pick the right one. The main ambiguity is around the campaign/messaging cluster: gambot_send_campaign, gambot_run_campaign, gambot_test_campaign, gambot_send_campaign_from_excel, and gambot_send_template could be confused, though the descriptions do draw useful boundaries.
All tool names follow the gambot_<verb>_<object> snake_case pattern with consistent verbs like get, list, create, update, delete, send, run, and test. Even longer names like get_signature_link and send_campaign_from_excel are predictable extensions of the same convention.
78 tools is far beyond a practical MCP surface and beyond the 50+ calibration threshold. The server merges many products (CRM, campaigns, documents, signatures, billing, onboarding, payments) into one namespace, which will likely overwhelm agent context and select a request. Consolidating related tools into smaller servers or higher-level operations would be far more appropriate.
The surface is broad but has significant lifecycle gaps: no list_contacts, no delete/update for many templates, no deletion for quotes/invoices/orders/tasks/leads/cases, and form/document/signature tools are mostly read/link-only rather than fully managed. These gaps will typically cause agent failures when users attempt standard cleanups or changes.
Maintenance
Related MCP Connectors
Run WhatsApp Business campaigns from any AI assistant: contacts, segments, and broadcasts.
WhatsApp CRM for AI agents: search contacts, read chats, manage the sales pipeline, send messages.
Send WhatsApp messages and templates, manage chats, contacts, broadcasts and AI agents.
WhatsApp CRM: inbox, contacts, deals, campaigns, AI agents, automations, ads and reports.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to send WhatsApp messages, templates, and retrieve media through the WhatsApp Cloud API. Provides webhook handling and seamless integration with Meta's WhatsApp Business platform.23ISC
- AlicenseBqualityCmaintenanceEnables AI assistants to manage WhatsApp business operations including chatbots, broadcasts, campaigns, and contacts through 120+ MCP tools.10046 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage omnichannel CRM data (WhatsApp, Instagram, Facebook) via the official API, including leads, deals, pipelines, activities, tags, products, conversations, lists, attachments, and notes.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage WhatsApp instances, send messages and campaigns, handle incoming messages, webhooks, members, and metrics through 30 authenticated tools, with an optional WhatsApp-to-assistant bridge.Apache 2.0