J
jevil25/whatsapp-messaging-api-mcp
Send WhatsApp messages from Claude, Cursor, or any MCP client.
更新 2026-11-16
在 GitHub 查看 ↗直链 · 无中转页
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 0 ★ · jevil25/whatsapp-messaging-api-mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
jevil25/whatsapp-messaging-api-mcp;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# WhatsApp Messaging API — MCP Server
以下摘录自该仓库的 README(片段)
Send WhatsApp messages from Claude, Cursor, or any MCP client. Create a session, scan a QR code, and send text, images and files — no Meta Business approval and no WhatsApp Business account required.
Wraps the WhatsApp Messaging API by Retention Stack.
## Quick start
1. Sign in at whatsapp-messaging.retentionstack.agency/start (free tier, no credit card) and copy a key from the console:
a session token (ch_live_...) for one number. Tools then need no session name.
an account key (ak_live_...) for every number on your account. Needed for create_session; pass session to the other tools.
2. Add this to your MCP client config (Claude Desktop: claude_desktop_config.json):
json
"mcpServers": {
"whatsapp": {
"command": "npx",
"args": ["-y", "whatsapp-messaging-api-mcp"],
"env": {
"WHATSAPP_API_KEY": "ch_live_your_session_token"
3. Restart the client. Ask it to create a WhatsApp session and show you the QR code.
Nothing to install or build — npx fetches the package on first run.
## Tools
| Tool | Description |
| list_sessions | List all sessions on this API key |
| create_session | Create a new session (account key only) |
| get_session_status | Check a session's current status |
| get_qr_code | Get the QR code to authenticate a session |
| request_pairing_code | Get an 8-digit pairing code instead of a QR |
| check_contact_exists | Check if a phone number is on WhatsApp before sending |
| send_text_message | Send a text message |
| send_image | Send an image via URL |
| send_file | Send a file (PDF, document) via URL |
## Typical flow
1. create_session → get_qr_code → scan with WhatsApp (Settings → Linked Devices)
2. get_session_status until it reports WORKING. If it reports PASSKEY_REQUIRED or PASSKEY_CONFIRMATION_REQUIRED, finish linking in the console: the passkey is signed in a browser, which an MCP client cannot do.
3. check_contact_exists, then send_text_message / send_image / send_file
Sessions stay authenticated between runs, so steps 1-2 are one-time per number.
## Configuration
| Variable | Required | Description |
| WHATSAPP_API_KEY | yes | A session token (ch_live_...) or account key (ak_live_...). The server exits on startup if it is missing. |
The key is read from the environment and sent only to the API host. It is never logged.
Upgrading from 1.x: earlier versions used a RapidAPI key, which no longer works. Replace it with a session token or account key from the console.
## Local development
bash
Wraps the WhatsApp Messaging API by Retention Stack.
## Quick start
1. Sign in at whatsapp-messaging.retentionstack.agency/start (free tier, no credit card) and copy a key from the console:
a session token (ch_live_...) for one number. Tools then need no session name.
an account key (ak_live_...) for every number on your account. Needed for create_session; pass session to the other tools.
2. Add this to your MCP client config (Claude Desktop: claude_desktop_config.json):
json
"mcpServers": {
"whatsapp": {
"command": "npx",
"args": ["-y", "whatsapp-messaging-api-mcp"],
"env": {
"WHATSAPP_API_KEY": "ch_live_your_session_token"
3. Restart the client. Ask it to create a WhatsApp session and show you the QR code.
Nothing to install or build — npx fetches the package on first run.
## Tools
| Tool | Description |
| list_sessions | List all sessions on this API key |
| create_session | Create a new session (account key only) |
| get_session_status | Check a session's current status |
| get_qr_code | Get the QR code to authenticate a session |
| request_pairing_code | Get an 8-digit pairing code instead of a QR |
| check_contact_exists | Check if a phone number is on WhatsApp before sending |
| send_text_message | Send a text message |
| send_image | Send an image via URL |
| send_file | Send a file (PDF, document) via URL |
## Typical flow
1. create_session → get_qr_code → scan with WhatsApp (Settings → Linked Devices)
2. get_session_status until it reports WORKING. If it reports PASSKEY_REQUIRED or PASSKEY_CONFIRMATION_REQUIRED, finish linking in the console: the passkey is signed in a browser, which an MCP client cannot do.
3. check_contact_exists, then send_text_message / send_image / send_file
Sessions stay authenticated between runs, so steps 1-2 are one-time per number.
## Configuration
| Variable | Required | Description |
| WHATSAPP_API_KEY | yes | A session token (ch_live_...) or account key (ak_live_...). The server exits on startup if it is missing. |
The key is read from the environment and sent only to the API host. It is never logged.
Upgrading from 1.x: earlier versions used a RapidAPI key, which no longer works. Replace it with a session token or account key from the console.
## Local development
bash
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/jevil25-whatsapp-messaging-api-mcp/)
- 来源
- awesome · https://github.com/jevil25/whatsapp-messaging-api-mcp
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。