WhatsApp MCP Server
Manage WhatsApp Business templates and send messages from Claude, ChatGPT, Cursor, VS Code Copilot, or any MCP-compatible client — powered by the Meta Cloud API.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
uvx jina-whatsapp-mcp==0.1.0Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
META_ACCESS_TOKEN=<secret> META_WABA_ID=<value> META_PHONE_NUMBER_ID=<value> META_APP_ID=<value> META_API_VERSION=<value> claude mcp add nakulben-whatsapp-mcp -- uvx jina-whatsapp-mcp==0.1.0在終端機中執行。
{ "mcpServers": { "nakulben-whatsapp-mcp": { "command": "uvx", "args": [ "jina-whatsapp-mcp==0.1.0" ], "env": { "META_ACCESS_TOKEN": "<secret>", "META_WABA_ID": "<value>", "META_PHONE_NUMBER_ID": "<value>", "META_APP_ID": "<value>", "META_API_VERSION": "<value>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
Manage WhatsApp Business templates and send messages from Claude, ChatGPT, Cursor, VS Code Copilot, or any MCP-compatible client — powered by the Meta Cloud API.
WhatsApp MCP Server — Manage templates & send messages via Claude, Cursor, or any MCP client. Meta Cloud API.
| Tool | Description |
|---|---|
validate_template | Validate a template payload before submitting to Meta |
create_template | Submit a template for Meta approval |
list_templates | List templates with optional filters (status, category, name) |
get_template_detail | Get full details of a template by ID |
check_template_status | Quick status check for a template |
delete_template | Delete a template by name |
send_template_message | Send an approved template to a phone number |
send_bulk_template_messages | Send an approved template to multiple phone numbers |
8 tools covering the full template lifecycle: create → validate → approve → send.
git clone https://github.com/nakulben/whatsapp-mcp.git
cd whatsapp-mcp
python -m venv venv
source venv/bin/activate # Windows: venv\Scripts\activate
pip install -r requirements.txt
cp .env.example .env
META_ACCESS_TOKEN=your_access_token
META_WABA_ID=your_whatsapp_business_account_id
META_PHONE_NUMBER_ID=your_phone_number_id
META_APP_ID=your_app_id # Optional, for media uploads
META_API_VERSION=v24.0 # Optional, defaults to v24.0
Environment variables are used by all modes — local stdio and hosted remote.
How to get these? Go to Meta for Developers, create or select your app, navigate to WhatsApp > API Setup.
The server supports 3 transport modes:
For HTTP transports, you can customize host/port:
python -m whatsapp_mcp --transport streamable-http --host 0.0.0.0 --port 8000
Add to claude_desktop_config.json:
{
"mcpServers": {
"whatsapp": {
"command": "/path/to/whatsapp-mcp/venv/bin/python",
"args": ["-m", "whatsapp_mcp"],
"env": {
"META_ACCESS_TOKEN": "your_access_token",
"META_WABA_ID": "your_waba_id",
"META_PHONE_NUMBER_ID": "your_phone_number_id",
"META_APP_ID": "your_app_id"
}
}
}
}
Claude.ai connects to remote MCP servers as custom connectors. The connection originates from Anthropic's cloud servers, not from your machine.
python -m whatsapp_mcp --transport streamable-http --host 0.0.0.0 --port 8001
https://your-domain.com/mcp/)Note: Claude.ai does not support custom request headers. The server must be pre-configured with Meta credentials via environment variables. Each hosted server serves one WhatsApp Business Account.
location /mcp/ {
proxy_pass http://127.0.0.1:8001/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_read_timeout 86400;
}
ChatGPT supports remote MCP servers via the Responses API. It supports both Streamable HTTP and SSE transports.
Option 1 — Server pre-configured with env vars (simplest):
from openai import OpenAI
client = OpenAI()
resp = client.responses.create(
model="gpt-4.1",
tools=[{
"type": "mcp",
"server_label": "whatsapp",
"server_url": "https://your-domain.com/mcp/",
"require_approval": "never",
}],
input="List all my approved templates",
)
Option 2 — Per-request credentials via Bearer token:
Encode your Meta credentials as base64 JSON and pass them in the authorization field.
OpenAI forwards this value as the Authorization header to your MCP server:
# Create the token
echo -n '{"access_token":"EAA...","phone_number_id":"123","waba_id":"456"}' | base64
# Output: eyJhY2Nlc3NfdG9rZW4iOiJFQUEuLi4iLCJwaG9uZV9udW1iZXJfaWQiOiIxMjMiLCJ3YWJhX2lkIjoiNDU2In0=
resp = client.responses.create(
model="gpt-4.1",
tools=[{
"type": "mcp",
"server_label": "whatsapp",
"server_url": "https://your-domain.com/mcp/",
"authorization": "eyJhY2Nlc3NfdG9rZW4iOiJFQUEuLi4iLCJwaG9uZV9udW1iZXJfaWQiOiIxMjMiLCJ3YWJhX2lkIjoiNDU2In0=",
"require_approval": "never",
}],
input="List all my approved templates",
)
Note: ChatGPT only supports remote MCP servers (no local stdio). Your server must be publicly accessible over HTTPS.
Add to .cursor/mcp.json in your project:
{
"mcpServers": {
"whatsapp": {
"command": "/path/to/whatsapp-mcp/venv/bin/python",
"args": ["-m", "whatsapp_mcp"]
}
}
}
Add to .vscode/mcp.json:
{
"servers": {
"whatsapp": {
"type": "stdio",
"command": "/path/to/whatsapp-mcp/venv/bin/python",
"args": ["-m", "whatsapp_mcp"]
}
}
}
For programmatic access or custom MCP clients, you can pass per-request credentials instead of relying on server env vars. Two methods are supported:
Method 1 — Bearer token (recommended):
Base64-encode a JSON object with your Meta credentials:
# Create the token
TOKEN=$(echo -n '{"access_token":"EAA...","phone_number_id":"123","waba_id":"456"}' | base64)
# Use it
curl -H "Authorization: Bearer $TOKEN" https://your-server.com/mcp/ ...
Required fields: access_token, phone_number_id, waba_id. Optional: app_id, api_version.
Method 2 — X-Meta- headers:*
If neither Bearer token nor X-Meta-* headers are present, the server falls back to environment variables.
Once connected, just talk to your AI assistant:
"Create a marketing template called
summer_salewith a header image, body text about 50% off, and a Shop Now button"
"List all my approved templates"
"Send the
order_confirmationtemplate to +919876543210 with order number ORD-456"
"Validate this template before I submit it: ..."
"Check the status of template ID 123456789"
Meta's API has 2 template categories(excluding Authentication). Within each category, templates can have different structural variants — each with its own component layout and validation rules.
How routing works: When you call
create_template, the server inspects the components to auto-detect the structural variant (e.g., presence ofcards[]→ Carousel,CATALOGbutton → Catalog) and applies the correct validator. You just passcategory: "MARKETING"or"UTILITY"— the variant is determined from the component structure.
pip install pytest pytest-asyncio
python -m pytest tests/ -v
whatsapp-mcp/
├── whatsapp_mcp/
│ ├── __init__.py # Package version
│ ├── __main__.py # Entry point (python -m whatsapp_mcp)
│ ├── config.py # Environment config loader
│ ├── meta_api.py # Async Meta Graph API client
│ ├── middleware.py # ASGI middleware for per-request credentials
│ ├── server.py # MCP server with 8 tools
│ ├── models/ # Pydantic data models
│ │ ├── body.py # Body component
│ │ ├── header.py # Header component (text/image/video/document)
│ │ ├── footer.py # Footer component
│ │ ├── buttons.py # Button types (URL, phone, quick reply, etc.)
│ │ ├── buttons_component.py
│ │ ├── enums.py # Template categories, types, formats
│ │ └── order_models.py # Order-related models (checkout templates)
│ └── validators/
│ ├── create/ # 12 template creation validators
│ └── send/ # 11 template send validators
├── tests/
│ ├── test_validators.py # Validator tests
│ ├── test_meta_api.py # API client tests (mocked HTTP)
│ └── test_tools.py # MCP tool registration & helper tests
├── .env.example
├── requirements.txt
├── LICENSE # MIT
└── ROADMAP.md
whatsapp_business_messaging and whatsapp_business_management permissionsSee ROADMAP.md for planned features.
MIT — see LICENSE.
Built by Jina Connect — the WhatsApp Business CX platform.
WhatsApp MCP Server — Manage templates & send messages via Claude, Cursor, or any MCP client. Meta Cloud API.
{ "mcpServers": { "nakulben-whatsapp-mcp": { "command": "uvx", "args": [ "jina-whatsapp-mcp==0.1.0" ], "env": { "META_ACCESS_TOKEN": "<secret>", "META_WABA_ID": "<value>", "META_PHONE_NUMBER_ID": "<value>", "META_APP_ID": "<value>", "META_API_VERSION": "<value>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:META_ACCESS_TOKEN, META_WABA_ID, META_PHONE_NUMBER_ID, META_APP_ID, META_API_VERSION。
Whatsapp 透過 stdio 在本機執行。
上次檢查時間:2026-10-28。 WhatsApp MCP Server — Manage templates & send messages via Claude, Cursor, or any MCP client. Meta Cloud API.