API Tools
wasapflow.com
Provides tools for integrating and managing the official WhatsApp Business API via WasapFlow Bridge, including setup guidance, documentation search, and account/number status.
ENDPOINT 1
https://officialapi.wasapflow.com/bridge/mcp
MCP server metadata
- Name
- wasapflow-bridge
- Version
- 1.0.0
WasapFlow Bridge gives your own SaaS or CRM the official WhatsApp Business API (Meta Cloud API) without becoming a Meta Tech Provider. Pricing: $10 USD/month per 3 WhatsApp Business Accounts; Meta bills message charges directly. Use bridge_get_started first when helping someone integrate. Use bridge_docs_search / bridge_docs_section to read the API reference before writing integration code — the docs are always current. Tools that call the live API need a partner key (header x-partner-key); without one they explain how to get it. Base URL for code you write: https://officialapi.wasapflow.com/bridge/v1. Never print the partner key or webhook secret back to the user.
Known tools 15
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.
Potential side effectsbridge_docs_searchSearch the WasapFlow Bridge API reference, partner guide and changelog.
Inferred read-onlybridge_docs_sectionReturn the full text of one section (with its sub-sections) of the WasapFlow Bridge docs, e.
Inferred read-onlybridge_list_numbersList the WhatsApp Business Accounts (client numbers) registered to this partner, with status.
Inferred read-onlybridge_number_statusLive status of a number from Meta: verified name, quality rating, messaging limit, name status.
Inferred read-onlybridge_connect_linkCreate a short-lived (30 min) link that a business opens to connect its WhatsApp number through Meta Embedded Signup (Coexistence supported).
Potential side effectsbridge_send_templateSend an approved template (works outside the 24-hour window).
Potential side effectsbridge_list_templatesList the message templates of a number with their approval status.
Potential side effectsbridge_failed_webhooksWebhook events Bridge could not deliver to your webhook URL (with the error).
Inferred read-onlybridge_retry_webhooksRedeliver one failed webhook event (event_id) or all of them (omit event_id) after the webhook endpoint is fixed.
Inferred read-onlybridge_usageCurrent Bridge plan: active WhatsApp numbers, slots and the monthly Bridge fee.
Inferred read-onlybridge_call_apiCall any WasapFlow Bridge endpoint not covered by the other tools (see bridge_docs_search for paths).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.wasapflow-bridge]
url = "https://officialapi.wasapflow.com/bridge/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"wasapflow-bridge": {
"type": "http",
"url": "https://officialapi.wasapflow.com/bridge/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: wasapflow-bridge
Remote MCP URL: https://officialapi.wasapflow.com/bridge/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"wasapflow-bridge": {
"url": "https://officialapi.wasapflow.com/bridge/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"wasapflow-bridge": {
"type": "http",
"url": "https://officialapi.wasapflow.com/bridge/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "wasapflow-bridge",
"transport": "streamable-http",
"url": "https://officialapi.wasapflow.com/bridge/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for wasapflow.com was fetched 2026-11-04T17:28:47.808Z.
wasapflow.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.