Send WhatsApp campaigns: templates, audiences, surveys, inbox replies, delivery webhooks.
Connect Runs on your machine
claude mcp add whatsapp-campaigns -e WA_GATEWAY_URL=<WA_GATEWAY_URL> -e WA_AGENT_KEY=<WA_AGENT_KEY> -- npx -y @wa-campaigns/[email protected]
{
"mcpServers": {
"whatsapp-campaigns": {
"command": "npx",
"args": [
"-y",
"@wa-campaigns/[email protected]"
],
"env": {
"WA_GATEWAY_URL": "<WA_GATEWAY_URL>",
"WA_AGENT_KEY": "<WA_AGENT_KEY>"
}
}
}
}
{
"mcpServers": {
"whatsapp-campaigns": {
"command": "npx",
"args": [
"-y",
"@wa-campaigns/[email protected]"
],
"env": {
"WA_GATEWAY_URL": "<WA_GATEWAY_URL>",
"WA_AGENT_KEY": "<WA_AGENT_KEY>"
}
}
}
}
{
"servers": {
"whatsapp-campaigns": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wa-campaigns/[email protected]"
],
"env": {
"WA_GATEWAY_URL": "<WA_GATEWAY_URL>",
"WA_AGENT_KEY": "<WA_AGENT_KEY>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
WA_GATEWAY_URLOptional | Optional. Base URL of the WhatsApp Campaigns agent gateway; defaults to the hosted production gateway. Set it only to target dev or a local gateway — a key is tied to the environment it was minted in, so it must match the environment that issued WA_AGENT_KEY. |
WA_AGENT_KEYRequired, secret | Scoped agent key (rcsk_live_…) created in Settings → API keys. The rcsk_ prefix is not a mistake: one key shape serves both channels, and the channel is chosen per call. |
Details
| Package | @wa-campaigns/[email protected] (NPM, stdio) |
| First published | 8 Nov 2026 |
| Last updated | 8 Nov 2026 |
| Registry name | com.wa-campaigns/whatsapp-campaigns |
More communication servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
