MCP server for interacting with your LINE Official Account
Gambot WhatsApp Business API is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Send WhatsApp messages & templates and manage CRM, leads & campaigns via the Gambot WhatsApp API.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'GAMBOT_TOKEN=${GAMBOT_TOKEN}' --transport stdio gambot-whatsapp-business-api-mcp '--' npx -y gambot-mcp
# 2 — ask your agent for something these tools do
# gambot_list_conversations, gambot_get_conversation_messages, gambot_list_templates and 76 more
It needs GAMBOT_TOKEN: this reads it from your environment, so export it first.
Gambot WhatsApp Business API costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Gambot WhatsApp Business API as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads GAMBOT_TOKEN (Your Gambot Token (gmbt_…) from Gambot Settings → General. Authorizes the server against your organization) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx GAMBOT_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'GAMBOT_TOKEN=${GAMBOT_TOKEN}' --transport stdio gambot-whatsapp-business-api-mcp '--' npx -y gambot-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: GAMBOT_TOKEN — Your Gambot Token (gmbt_…) from Gambot Settings → General. Authorizes the server against your organization.. You set it in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
79 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List conversations (contacts) ordered by most recent message.
No parameter schema on file.
Read the message history for a single conversation.
No parameter schema on file.
List all WhatsApp templates for the organization.
No parameter schema on file.
Get a single template by id, including Meta approval status.
No parameter schema on file.
Get the dynamic variables of a template.
No parameter schema on file.
Upload a public media URL (image/video/document) to Meta and get a reusable header_handle for a template
No parameter schema on file.
Get contact field definitions (base + custom/dynamic). Contacts store custom values as top-level keys —
No parameter schema on file.
Create a contact (returns the existing one if the phone is already known).
No parameter schema on file.
Fetch a contact by phone number.
No parameter schema on file.
Update a contact — only the provided fields are changed. Custom fields go under
No parameter schema on file.
Get lead field definitions: { baseFields, customFields }. Custom lead values are stored under a nested
No parameter schema on file.
Create a CRM lead (contact created if missing, optional template send). Accepts all base lead fields
No parameter schema on file.
Update a lead — only the provided fields are changed. Accepts any base field plus a nested
No parameter schema on file.
Get case (פנייה) field definitions: { baseFields, customFields }. Custom case values are stored under a
No parameter schema on file.
Create a case (support ticket / פנייה). Accepts base fields plus a nested
No parameter schema on file.
Update a case — only the provided fields are changed. Accepts base fields plus a nested
No parameter schema on file.
Create a task (optionally linked to a contact via contactPhone).
No parameter schema on file.
List leads (paginated).
No parameter schema on file.
Get a single lead by id.
No parameter schema on file.
List cases (paginated).
No parameter schema on file.
Get a single case by id.
No parameter schema on file.
List tasks for the organization.
No parameter schema on file.
Get a single task by id.
No parameter schema on file.
Update a task — only the provided fields are changed.
No parameter schema on file.
Create a price quote. quoteData holds the quote fields (title, items, total, contact…).
No parameter schema on file.
List price quotes (paginated).
No parameter schema on file.
Get a single quote by id.
No parameter schema on file.
Update quote fields (partial).
No parameter schema on file.
Create an invoice draft. invoiceData holds the invoice fields.
No parameter schema on file.
List invoices (paginated).
No parameter schema on file.
Get a single invoice by id.
No parameter schema on file.
Update invoice fields (blocked once issued/locked).
No parameter schema on file.
Issue an invoice — locks it and assigns the official document number.
No parameter schema on file.
Create a store order. Body holds order fields (customer, items, total…).
No parameter schema on file.
List orders (optionally filtered by status / store / date range).
No parameter schema on file.
Get a single order by id.
No parameter schema on file.
Update order fields (merge).
No parameter schema on file.
List e-signature documents (newest first).
No parameter schema on file.
Get a single e-signature document, including its signing results.
No parameter schema on file.
Get the signing link(s) to distribute for an existing signature document (one per signer). Share with signers via WhatsApp/email/SMS.
No parameter schema on file.
List web forms.
No parameter schema on file.
Get a single web form definition.
No parameter schema on file.
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
No parameter schema on file.
Get submissions (results) for a web form.
No parameter schema on file.
List document templates.
No parameter schema on file.
Get a single document template.
No parameter schema on file.
Get fill-only submissions generated from a document template.
No parameter schema on file.
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.
No parameter schema on file.
Create an organization user (team member). Sends a welcome email + WhatsApp invite.
No parameter schema on file.
List organization users (excluding system bots).
No parameter schema on file.
Get a single user by id.
No parameter schema on file.
Update user fields — only the provided ones are changed.
No parameter schema on file.
Disable a user (status = inactive).
No parameter schema on file.
Enable a user (status = active).
No parameter schema on file.
Permanently delete an organization user (removes both the auth account and the profile). This is irreversible —
No parameter schema on file.
List all broadcast campaigns for the organization.
No parameter schema on file.
List scheduled campaigns that are waiting to run.
No parameter schema on file.
Get a single campaign by id.
No parameter schema on file.
Get the run results/report for a campaign (sent/delivered/read/replies/clicks).
No parameter schema on file.
Update a campaign (send the full campaign object).
No parameter schema on file.
Delete a campaign by id.
No parameter schema on file.
Run an existing (saved) campaign by id now (resolves recipients and executes).
No parameter schema on file.
Run an ad-hoc campaign WITHOUT saving it first. Provide an audience (recipientPhoneNumbers, excelRecipients or filters)
No parameter schema on file.
Send a single-recipient TEST of a template or free-text message. Great for previewing before a full broadcast.
No parameter schema on file.
List the organization
No parameter schema on file.
Get a single bot/automation with its full step definition (trigger + actions).
No parameter schema on file.
Create a bot that automatically replies to an incoming WhatsApp message. Trigger on specific keyword(s)
No parameter schema on file.
Create a bot that reacts when a contact taps a quick-reply BUTTON on a template you sent (e.g. after a campaign).
No parameter schema on file.
Create a menu bot: an opening template with quick-reply buttons that route each tap to a reply.
No parameter schema on file.
Turn a bot on (active) or off (inactive).
No parameter schema on file.
Delete a bot/automation by id.
No parameter schema on file.
Advanced: create a bot from a full botomation object when the high-level builders aren
No parameter schema on file.
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.
No parameter schema on file.
Generate a unique organization name from a company name + tax id (adds a suffix if taken).
No parameter schema on file.
List phone numbers available to purchase for a country (via Twilio), so you can pick one to buy as the account
No parameter schema on file.
Verify a card with the clearing provider (Tranzila) and save its token to an organization, so an AI agent with the customer
No parameter schema on file.
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.
No parameter schema on file.
Get the hosted page URL where the customer completes Meta Embedded Signup (the Facebook popup) to connect their WhatsApp Business account.
No parameter schema on file.
Complete Meta Embedded Signup by exchanging the authorization code returned by the Facebook popup. Registers the WABA, subscribes webhooks and registers the phone number.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Gambot WhatsApp Business API or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.8.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Gambot WhatsApp Business API can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.