WhatsApp Campaigns

com.wa-campaignsPublished by wa-campaigns.comv0.1.6Updated Oct 25, 2026

Send WhatsApp campaigns: templates, audiences, surveys, inbox replies, delivery webhooks.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that lets an assistant send WhatsApp campaigns — templates, audiences, surveys, inbox replies and delivery webhooks — through your WhatsApp-C

What you can do
Send WhatsApp campaigns, including templates, audiences and surveys, per the registry description. Handle inbox replies and delivery webhooks. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
When you run WhatsApp Campaigns and want an assistant to help build and send campaigns, manage audiences and surveys, or handle inbox replies and delivery webhooks from your own machine.
Requirements
Runs locally via npx from the npm package @wa-campaigns/agent-toolkit (Node.js required). Needs WA_AGENT_KEY, a scoped agent key created in Settings → API keys, and WA_GATEWAY_URL, the base URL of your agent gateway; the key must come from the same environment as that URL. Desktop only.
Before you install
Requires a live API key (WA_AGENT_KEY) that grants access to your WhatsApp Campaigns account. The server can send campaigns and replies to real recipients, so messages go out to third parties; review what the assistant is about to send before approving it.

Installation

In SourceWeft

  1. Open WhatsApp Campaigns in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.6LatestSep 21, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.