WasapFlow Bridge

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Marketing & social media
• You need to fill in: x-partner-key

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

claude mcp add --transport http bridge https://officialapi.wasapflow.com/bridge/mcp --header 'x-partner-key: your-value'

{
  "mcpServers": {
    "bridge": {
      "url": "https://officialapi.wasapflow.com/bridge/mcp",
      "headers": {
        "x-partner-key": "your-value"
      }
    }
  }
}

{
  "servers": {
    "bridge": {
      "type": "http",
      "url": "https://officialapi.wasapflow.com/bridge/mcp",
      "headers": {
        "x-partner-key": "your-value"
      }
    }
  }
}

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• x-partner-key secret HTTP header
  Partner key from partner.wasapflow.com → Integration. Optional: docs tools work without it.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• bridge_get_started

  Step-by-step plan to add the official WhatsApp Business API to the user's own CRM/SaaS with WasapFlow Bridge: account, card, keys, webhook, Connect WhatsApp button, first message. Call this first when someone wants to build or connect WhatsApp. No partner key needed.

• bridge_docs_search

  Search the WasapFlow Bridge API reference, partner guide and changelog. Returns matching sections with a preview. Use before writing integration code. No partner key needed.

• bridge_docs_section

  Return the full text of one section (with its sub-sections) of the WasapFlow Bridge docs, e.g. "Verify Incoming Webhooks", "Send Template Message", "Webhook Event Payloads", "Error Codes". No partner key needed.

• bridge_list_numbers

  List the WhatsApp Business Accounts (client numbers) registered to this partner, with status.

• bridge_number_status

  Live status of a number from Meta: verified name, quality rating, messaging limit, name status.

• bridge_connect_link

  Create a short-lived (30 min) link that a business opens to connect its WhatsApp number through Meta Embedded Signup (Coexistence supported). Share the returned connect_url with the business owner.

• bridge_send_text

  Send a text message from a connected number. Free-form text only reaches people who messaged that number in the last 24 hours; otherwise use bridge_send_template. This sends a real message.

• bridge_send_template

  Send an approved template (works outside the 24-hour window). components follows the Meta Cloud API format. This sends a real message and Meta may charge for it.

• bridge_send_marketing

  Send an approved MARKETING template through Meta's Marketing Messages API (quality-based delivery, marketing metrics). Not onboarded yet? Meta falls back to Cloud API unless product_policy is STRICT. This sends a real message and Meta charges for it.

• bridge_list_templates

  List the message templates of a number with their approval status.

• bridge_failed_webhooks

  Webhook events Bridge could not deliver to your webhook URL (with the error). Use when incoming messages are missing in the CRM.

• bridge_retry_webhooks

  Redeliver one failed webhook event (event_id) or all of them (omit event_id) after the webhook endpoint is fixed.

• bridge_usage

  Current Bridge plan: active WhatsApp numbers, slots and the monthly Bridge fee.

• bridge_open_ticket

  Open a WasapFlow support ticket. Include what happened, when (with timezone), the exact error (Meta code, fbtrace_id), what was tried and the business impact.

• bridge_list_tickets

  List support tickets and replies status.

• bridge_call_api

  Call any WasapFlow Bridge endpoint not covered by the other tools (see bridge_docs_search for paths). Irreversible endpoints need {"confirm": true} in the body. Confirm with the user before any call that sends, deletes or changes something.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ! Caution

  Maker matches the repo

  The publisher (wasapflow.com) is not the repo owner (kobaranteguh); someone else may have listed it

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 430 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 16 tool descriptions and found no hidden instructions to the AI

Compared with others in Marketing & social mediai

• More stars than 0% of the other 2956 servers in this category
• Published to the registry more recently than 92% of the other 2956 servers in this category
• Basic checks equal to or better than 48% of the other 2956 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

   git clone https://github.com/kobaranteguh/whatsapp-crm-starter.git

3. **Keys.** Open portal → **Integration** and copy the Partner Key and Webhook Secret into `.env`.

   npm start

claude mcp add --transport http wasapflow https://officialapi.wasapflow.com/bridge/mcp --header "x-partner-key: wf_..."

{ "mcpServers": { "wasapflow": { "url": "https://officialapi.wasapflow.com/bridge/mcp", "headers": { "x-partner-key": "wf_..." } } } }