Skip to content
MCP server

WhatsApp Campaigns

Run WhatsApp campaigns, surveys and inbox replies from an AI agent over MCP

Runs locallyStatus and history
Install
Platforms
API, CLI, whatsapp
Runs
Locally
Version
0.1.11
Listing updated
today

Similar MCP servers

About WhatsApp Campaigns

WhatsApp Campaigns is an MCP server for communication. It runs locally on your machine and is started by your AI client.

The docs describe a single hosted gateway with 48 calls, listed with their HTTP method, path and required scope. The MCP server and a CLI are generated from the same catalogue, and an OpenAPI 3.1 document is published too. The gateway's own capabilities call tells an agent what it exists to do and which of those things its key is allowed to do.

Templates are the core: create, clone, duplicate, render, update, submit for approval and delete. Around them sit conversational surveys (create, test-send, send, collect results), audiences and contacts, an inbox with conversations that can be assigned, grounding knowledge documents, media upload, webhooks and a usage report.

Authentication uses a scoped agent key as bearer token. Keys are minted by an org admin, shown once, stored only as a SHA-256 hash and revocable. The master key is not honoured on this surface, so an agent key cannot reach admin routes. The registry entry notes that one rcsk_ key shape serves both WhatsApp and RCS, with the channel chosen per call.

Install

Run in a terminal

claude mcp add whatsapp-campaigns --env WA_AGENT_KEY='<WA_AGENT_KEY>' -- npx -y @wa-campaigns/agent-toolkit

Add to claude_desktop_config.json

{
  "mcpServers": {
    "whatsapp-campaigns": {
      "command": "npx",
      "args": [
        "-y",
        "@wa-campaigns/agent-toolkit"
      ],
      "env": {
        "WA_AGENT_KEY": "<WA_AGENT_KEY>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "whatsapp-campaigns": {
      "command": "npx",
      "args": [
        "-y",
        "@wa-campaigns/agent-toolkit"
      ],
      "env": {
        "WA_AGENT_KEY": "<WA_AGENT_KEY>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "whatsapp-campaigns": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@wa-campaigns/agent-toolkit"
      ],
      "env": {
        "WA_AGENT_KEY": "<WA_AGENT_KEY>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "whatsapp-campaigns": {
      "command": "npx",
      "args": [
        "-y",
        "@wa-campaigns/agent-toolkit"
      ],
      "env": {
        "WA_AGENT_KEY": "<WA_AGENT_KEY>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "whatsapp-campaigns": {
      "command": "npx",
      "args": [
        "-y",
        "@wa-campaigns/agent-toolkit"
      ],
      "env": {
        "WA_AGENT_KEY": "<WA_AGENT_KEY>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • WA_GATEWAY_URLOptional. 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_KEYScoped 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.Required

Tools this server provides (12)

Taken from the project documentation; the running server may differ.

search_templates
Gateway call search templates
create_template
Gateway call create template
clone_template
Gateway call clone template
render_template
Gateway call render template
submit_template
Gateway call submit template
send_survey
Gateway call send survey
create_audience
Gateway call create audience
import_contacts
Gateway call import contacts
list_conversations
Gateway call list conversations
assign_conversation
Gateway call assign conversation
create_webhook
Gateway call create webhook
get_usage
Gateway call get usage

What it does

Template lifecycle
Create, clone, render, update, submit and delete WhatsApp templates.
Conversational surveys
Build surveys, send test runs and read results.
Audience management
Create audiences, import contacts and list members.
Inbox and replies
List conversations, read them and assign them.
Grounding knowledge
Set, enable, disable and delete knowledge documents.
Delivery webhooks
Create, test, update and delete webhooks.
Scoped keys
Every route names the scope it needs.

Good for

  • Draft and submit a WhatsApp template through an agent
  • Run a survey and pull the results
  • Import contacts into a new audience
  • Route inbox conversations to teammates

More servers for the same service

WhatsApp Campaigns FAQ

How many calls are there?

The docs say 48 calls over one HTTP surface.

Is there an OpenAPI spec?

Yes, OpenAPI 3.1 generated from the gateway's tool catalogue.

How do I authenticate?

Set WA_AGENT_KEY to a scoped agent key created by an org admin.

Does the key work for RCS too?

The registry notes say the same rcsk_ key shape serves both channels.

How do I add WhatsApp Campaigns to Claude Code?

Run this command in your terminal: claude mcp add whatsapp-campaigns --env WA_AGENT_KEY='<WA_AGENT_KEY>' -- npx -y @wa-campaigns/agent-toolkit

What are the best alternatives to WhatsApp Campaigns?

The closest alternatives to WhatsApp Campaigns are TrendRadar, Google Ads + Meta Ads + SEO/GEO MCP, Getmitra, Calven and Discord.

Where this comes from

  • Description: written from the project's README and the project's website.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers