Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
WHATSAPP_ACCESS_TOKEN, WHATSAPP_PHONE_NUMBER_ID, WHATSAPP_BUSINESS_ACCOUNT_ID, WHATSAPP_GRAPH_VERSION标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"whatsapp-cloud": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-whatsapp-cloud"
],
"env": {
"WHATSAPP_ACCESS_TOKEN": "your-value",
"WHATSAPP_PHONE_NUMBER_ID": "your-value",
"WHATSAPP_BUSINESS_ACCOUNT_ID": "your-value",
"WHATSAPP_GRAPH_VERSION": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add whatsapp-cloud --env WHATSAPP_ACCESS_TOKEN=your-value --env WHATSAPP_PHONE_NUMBER_ID=your-value --env WHATSAPP_BUSINESS_ACCOUNT_ID=your-value --env WHATSAPP_GRAPH_VERSION=your-value -- npx -y @codespar/mcp-whatsapp-cloud运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"whatsapp-cloud": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-whatsapp-cloud"
],
"env": {
"WHATSAPP_ACCESS_TOKEN": "your-value",
"WHATSAPP_PHONE_NUMBER_ID": "your-value",
"WHATSAPP_BUSINESS_ACCOUNT_ID": "your-value",
"WHATSAPP_GRAPH_VERSION": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"whatsapp-cloud": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-whatsapp-cloud"
],
"env": {
"WHATSAPP_ACCESS_TOKEN": "your-value",
"WHATSAPP_PHONE_NUMBER_ID": "your-value",
"WHATSAPP_BUSINESS_ACCOUNT_ID": "your-value",
"WHATSAPP_GRAPH_VERSION": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
WHATSAPP_GRAPH_VERSION env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 codespar 验证,该账户拥有此仓库
代码最后更新于40天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:WHATSAPP_ACCESS_TOKEN, WHATSAPP_PHONE_NUMBER_ID, WHATSAPP_BUSINESS_ACCOUNT_ID
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于40天前,最新版本(0.2.2)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Vexa, emailmd, Gmail MCP Server
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Lean Gmail MCP server with auto authentication support
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for the WhatsApp Cloud API — Meta's official WhatsApp Business API, self-hosted on Meta infrastructure.
Direct Meta integration. No middleman, no provider markup. For merchants with an approved WhatsApp Business Account (WABA) who want Meta-direct pricing and full control over conversation, pricing category, and template lifecycle.
| Server | What it is | When to pick it |
|---|---|---|
| whatsapp-cloud (this) | Direct Meta Cloud API | Large merchants with approved WABA; lower cost at scale, no intermediary fees |
| z-api | Wrapper on top of Meta Cloud | Easy onboarding, instant QR-pair, extra helpers |
| evolution-api | Open-source wrapper | Self-hosted, community-driven |
| take-blip | Brazilian BSP wrapper | Enterprise Brazil, CCaaS features |
| zenvia | Brazilian BSP wrapper | Brazil omnichannel (SMS + WhatsApp) |
| Tool | Purpose |
|---|---|
send_text_message | Send a plain text message. |
send_template_message | Send an approved message template. |
send_media_message | Send an image, video, document, or audio. |
send_interactive_message | Send an interactive message (reply buttons or list). |
send_interactive_cta_url | Send an interactive message with a single CTA URL button. |
send_interactive_flow | Send a WhatsApp Flow message. |
send_location_message | Send a location pin with latitude/longitude and optional name/address. |
send_contacts_message | Send one or more contact cards (vCard-like). |
send_reaction_message | Send an emoji reaction on a previously received/sent message. |
send_typing_indicator | Show a typing indicator on a received message. |
mark_message_as_read | Mark an incoming message as read so the sender sees the blue double-check. |
upload_media | Upload a media file and get back a media_id reusable in send_media_message. |
retrieve_media_url | Resolve a media_id to a short-lived downloadable URL. |
delete_media | Delete an uploaded media asset by id. |
list_templates | List message templates on the WhatsApp Business Account. |
create_template | Submit a new template for Meta review. |
delete_template | Delete a message template from the WABA by name. |
get_business_profile | Read the WhatsApp business profile (about, description, email, websites, vertical, address) for the configu... |
update_business_profile | Update the business profile on the configured phone number. |
list_phone_numbers | List all phone numbers registered under the WhatsApp Business Account, including display name, quality rati... |
request_verification_code | Request Meta to send a verification code to the configured phone number via SMS or voice. |
verify_code | Submit the verification code received via SMS/voice after request_verification_code. |
npm install @codespar/mcp-whatsapp-cloud
WHATSAPP_ACCESS_TOKEN="EAAG..." # required (secret) — Meta system-user token
WHATSAPP_PHONE_NUMBER_ID="1234567890" # required — WABA phone number id WHATSAPP_BUSINESS_ACCOUNT_ID="9876543210" # required — WABA id (for templates) WHATSAPP_GRAPH_VERSION="v21.0" # optional — Meta bumps quarterly
Bearer token against the Graph API. Use a permanent system-user token from Meta Business Manager — user access tokens expire and will break production.
Authorization: Bearer <WHATSAPP_ACCESS_TOKEN>
send_template_message with a name + language + components.create_template, wait for Meta approval (minutes to hours), then use.5511999999999).Two paths:
link to send_media_message. Fastest, but Meta fetches on every send.upload_media once, reuse id on subsequent sends. Recommended for catalog assets.Uploaded media expires after ~30 days.
send_interactive_message expects a fully-formed interactive object. Example button payload:
{
"type": "button", "body": { "text": "Confirma seu pedido?" }, "action": { "buttons": [ { "type": "reply", "reply": { "id": "confirm", "title": "Confirmar" } }, { "type": "reply", "reply": { "id": "cancel", "title": "Cancelar" } } ] } }
See the Cloud API interactive reference for list payloads.
# stdio (default — for Claude Desktop, Cursor, etc)
npx @codespar/mcp-whatsapp-cloud
MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-whatsapp-cloud
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
MIT