Wabi

dev.getwabiPublished by getwabi.devOfficial publisherv0.1.2Updated Nov 5, 2026

WhatsApp Business on Meta's Cloud API: team inbox, templates, AI support agents and analytics.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Wabi connects an assistant to WhatsApp Business on Meta's Cloud API for a team inbox, message templates, AI support agents and analytics.

What you can do
  • Work with a WhatsApp Business team inbox on Meta's Cloud API.
  • Use message templates and AI support agents for customer conversations.
  • Review analytics on messaging activity.
  • Connect either through a remote endpoint or a local npm package over stdio.
When to use it
Useful when a team handles WhatsApp Business customer conversations and wants an assistant to work with the inbox, templates, support agents and analytics in the same place.
Requirements
A Wabi account with OAuth sign-in, plus a Wabi API key supplied as WABI_API_KEY (optional once the wabi login command has stored one). Runs as a remote endpoint or as the npm package @meterapp/wabi over stdio, which needs a local Node.js runtime. Network access to Wabi and Meta's Cloud API.
Before you install
Requires OAuth and a WABI_API_KEY credential, which grants access to the connected WhatsApp Business account. The server can act on customer conversations, templates and support agents, so changes may reach real customers. Review what data is sent to Wabi and Meta before use.

Installation

In SourceWeft

  1. Open Wabi in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.getwabi%2Fwabi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "wabi": {
      "type": "http",
      "url": "https://getwabi.dev/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.1.2LatestNov 5, 2026
  2. v0.1.1Nov 3, 2026
  3. v0.1.0Nov 3, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.