WhatsApp Campaigns

com.wa-campaignsPublished by wa-campaigns.comv0.1.10Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyCommunication & Collaboration Business & Commerce

Server details

Identifier: com.wa-campaigns/whatsapp-campaigns
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 21, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to wa-campaigns.com. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.wa-campaigns%2Fwhatsapp-campaigns.svg)](https://sourceweft.com/mcp/com.wa-campaigns%2Fwhatsapp-campaigns?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets an assistant run WhatsApp campaigns: templates, audiences, surveys, inbox replies and delivery webhooks.

What you can do: Send WhatsApp campaigns and manage the pieces around them.
Work with message templates and audiences.
Run surveys and reply to inbox conversations.
Track delivery through webhooks.
The channel is chosen per call, so the same key can serve both channels.
When to use it: Useful when you already run WhatsApp Campaigns and want an assistant to draft, send or follow up on campaigns, surveys and inbox replies without switching to the web app. It is a desktop-only local process, so it suits individual operators rather than shared server deployments.
Requirements: Runs locally over stdio via npx from the npm package @wa-campaigns/agent-toolkit, so Node.js is needed. Requires a WhatsApp Campaigns account and a scoped agent key in WA_AGENT_KEY, created in Settings → API keys. WA_GATEWAY_URL is optional and defaults to the hosted production gateway. Desktop only.

Before you install

The agent key is a live credential; keep it out of logs and shared configs. The server can send messages to real recipients and reply in inboxes, so actions are outward-facing and hard to undo. Only point WA_GATEWAY_URL at dev or a local gateway with a key minted for that environment.

Installation

In SourceWeft

Open WhatsApp Campaigns in the dashboard and add it to a workspace.
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

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

Version history

v0.1.10LatestSep 30, 2026
v0.1.9Sep 22, 2026
v0.1.7Sep 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.