WasapFlow Bridge

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.wasapflow/bridge and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 4 Nov 2026. Not supplied by the maker.

• 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

• 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

• 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.