WasapFlow MCP server
Which MCP servers are WasapFlow's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-11-04
- Registry namecom.wasapflow/bridgeverified in the MCP registry
The registry name sits under wasapflow.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-11-04
- Tools15
- Server calls itselfwasapflow-bridge
- Server version1.0.0
- Protocol version2025-06-18
On 2026-11-04 the server answered initialize and tools/list without a sign-in. First answer in 408 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- Keep approval on for bridge_send_text, bridge_send_template: they delete, send or pay without saying so.
- bridge_send_text, bridge_send_template change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 5 of 15 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer412 ms
- Space in an agent's context≈ 1,662 tokensthe definitions of all its tools (15), which an agent carries on every turn
- Tool definitionsA · 94 of 100
- Typed results0 of 15 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 5 of 15
Worth a look
- Tools that delete, send or pay, marked as not destructive: bridge_send_text, bridge_send_template
- Tools that change data, on a server that answers without a sign-in: bridge_send_text, bridge_send_template
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
bridge_get_startedStep-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…
bridge_docs_searchSearch 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_sectionReturn 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_numbersList the WhatsApp Business Accounts (client numbers) registered to this partner, with status.
bridge_number_statusLive status of a number from Meta: verified name, quality rating, messaging limit, name status.
bridge_connect_linkCreate 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_textSend 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_templateSend 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_list_templatesList the message templates of a number with their approval status.
bridge_failed_webhooksWebhook events Bridge could not deliver to your webhook URL (with the error). Use when incoming messages are missing in the CRM.
bridge_retry_webhooksRedeliver one failed webhook event (event_id) or all of them (omit event_id) after the webhook endpoint is fixed.
bridge_usageCurrent Bridge plan: active WhatsApp numbers, slots and the monthly Bridge fee.
bridge_open_ticketOpen 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_ticketsList support tickets and replies status.
bridge_call_apiCall 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.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"bridge": {
"type": "http",
"url": "https://officialapi.wasapflow.com/bridge/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http wasapflow https://officialapi.wasapflow.com/bridge/mcpclaude.ai, ChatGPT and other clients: add https://officialapi.wasapflow.com/bridge/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.