Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
MCP gateway for WhatsApp via Green API: messaging, contacts, groups and instance management.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
X-Instance-Id, X-Api-Token标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http whatsapp https://mcp.green-api.com/mcp --header 'X-Instance-Id: your-value' --header 'X-Api-Token: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"whatsapp": {
"url": "https://mcp.green-api.com/mcp",
"headers": {
"X-Instance-Id": "your-value",
"X-Api-Token": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"whatsapp": {
"type": "http",
"url": "https://mcp.green-api.com/mcp",
"headers": {
"X-Instance-Id": "your-value",
"X-Api-Token": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
X-Instance-Id 机密 必填 HTTP headerX-Api-Token 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 green-api.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:X-Instance-Id, X-Api-Token
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.2)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Vexa, emailmd, MCP WhatsApp Cloud
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP gateway for GREEN-API WhatsApp. Lets AI agents (Claude Desktop, OpenClaw, Cursor, and others) send messages, manage instances, and receive notifications via WhatsApp using the Model Context Protocol.
Send text messages, files by URL, locations, contacts, polls. Forward and edit messages. Manage groups (create, fetch data, add/remove participants). Check phone numbers for WhatsApp, fetch contacts and their info. Get instance state and settings, QR code for authorization. Receive incoming notifications via polling or an HTTP receiver. Partner API for creating/deleting instances. Multi-instance support in a single gateway. Prompt templates for common scenarios (customer support, broadcasts). Prometheus metrics and OpenTelemetry.
Instructions for connecting the MCP server can be found on our website
Clean Architecture (Ports & Adapters):
cmd/server/main.go — entry point, DI wiring
internal/ domain/ — business entities, errors, constants (zero dependencies) application/ — ports (interfaces) infrastructure/ auth.go — CredentialManager (in-memory credential store) config/config.go — YAML + env configuration greenapi/client.go — WhatsApp client via Go SDK mcp/ server.go — MCP server (stdio/sse) tools.go — MCP tools registration resources.go — MCP resources prompts.go — MCP prompts webhook/ bridge.go — polling bridge receiver.go — HTTP receiver
go build -o green-api-mcp-gateway ./cmd/server
Requires Go 1.25+.
The server supports four transports, selected via server.transport (or the GREEN_API_TRANSPORT env var):
| Transport | Endpoints (relative to host:port) | Use case |
|---|---|---|
stdio | stdin/stdout | Local CLIs (Claude Desktop, Cursor) launching the binary. |
sse | GET / (stream) + POST /message | Legacy MCP clients (SSE only). |
http | POST/GET /mcp | Streamable HTTP (MCP 2025-03-26+) — preferred for new clients. |
hybrid | /sse + /message and /mcp on one port | Public server: serves both legacy SSE and Streamable HTTP. |
All HTTP-based transports also expose:
GET /health, GET /healthz — health probes (no auth)GET /favicon.ico, GET /favicon.png — GREEN-API iconWhen auth.mode: proxy is enabled, the OAuth 2.0 PKCE endpoints are added too:
GET /.well-known/oauth-authorization-server — RFC 8414 metadataGET /.well-known/oauth-protected-resource — RFC 9728 metadataGET /authorize — browser-facing authorization formPOST /token — token exchangeserver:
transport: stdio # stdio | sse | http | hybrid port: 8090
auth: mode: config # config | proxy cache_ttl: 300 # seconds (proxy mode only)
green_api: instances:
webhook: mode: polling polling_timeout: 20
rate_limit: requests_per_second: 10 burst: 20
logging: level: info format: text
Environment variables take precedence over the YAML config:
The variables below cover both deployment modes. Credentials variables (GREEN_API_INSTANCE_ID, GREEN_API_TOKEN, GREEN_API_URL) apply only to local stdio runs with auth.mode: config. For HTTP transports (sse on /sse + /message, http on /mcp, or hybrid) use auth.mode: proxy instead — credentials arrive in HTTP headers or via the built-in OAuth flow and the env credentials are ignored.
GREEN_API_INSTANCE_ID — instance IDGREEN_API_TOKEN — API tokenGREEN_API_URL — API base URL (defaults to https://api.green-api.com)GREEN_API_TRANSPORT — transport: stdio, sse, http, or hybridGREEN_API_PORT — HTTP port (defaults to 8090)GREEN_API_BASE_URL — public base URL (used for OAuth issuer/redirects, e.g. https://mcp.example.com)GREEN_API_WIDGET_DOMAIN — unique widget origin for ChatGPT Apps submission metadata (defaults to GREEN_API_BASE_URL, then https://mcp.green-api.com)GREEN_API_AUTH_MODE — config or proxyGREEN_API_AUTH_CACHE_TTL — proxy-auth credential cache TTL (seconds)GREEN_API_WEBHOOK_MODE — polling or receiverLOG_LEVEL — log levelLOG_FORMAT — text or json# With environment variables
export GREEN_API_INSTANCE_ID=1101000001 export GREEN_API_TOKEN=your_token ./green-api-mcp-gateway
./green-api-mcp-gateway --config config.yaml
Add to claude_desktop_config.json:
{
"mcpServers": { "whatsapp": { "command": "/path/to/green-api-mcp-gateway", "args": ["--config", "/path/to/config.yaml"] } } }
mcp:
servers:
docker build -t green-api-mcp-gateway .
docker run --rm -i \ -e GREEN_API_INSTANCE_ID=1101000001 \ -e GREEN_API_TOKEN=your_token \ green-api-mcp-gateway
whatsapp_send_message — text messagewhatsapp_send_file — file by URLwhatsapp_send_location — locationwhatsapp_send_contact — contact (vCard)whatsapp_send_poll — pollwhatsapp_forward_messages — forwardwhatsapp_edit_message — editwhatsapp_delete_message — deletewhatsapp_get_state — authorization statewhatsapp_get_settings — current settingswhatsapp_set_settings — update settingswhatsapp_get_qr — authorization QR codewhatsapp_connect — connect instancewhatsapp_disconnect — disconnect instancewhatsapp_get_contacts — contact listwhatsapp_get_contact_info — contact informationwhatsapp_check_whatsapp — phone number checkwhatsapp_create_group — create a groupwhatsapp_get_group_data — group datawhatsapp_add_group_participant — add a participantwhatsapp_remove_group_participant — remove a participantwhatsapp_leave_group — leave a groupwhatsapp_receive_notification — receive an incoming notification (long-poll)whatsapp_create_instance — create an instancewhatsapp_delete_instance — delete an instancewhatsapp_get_instances — list instanceswhatsapp://instance/{id}/state — instance statewhatsapp://instance/{id}/settings — instance settingswhatsapp_customer_support — template for customer supportwhatsapp_broadcast — template for broadcast messaginggo test ./...
gofmt -w . GOOS=linux GOARCH=amd64 go build -o green-api-mcp-gateway-linux ./cmd/server
MIT — see LICENSE.