Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
Governed email for AI agents: a sandbox inbox to read and send from, human approval to go external.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
MAILBUTTONS_API_KEY, MAILBUTTONS_API_URL, Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"mailbuttons": {
"command": "npx",
"args": [
"-y",
"@mailbuttons/mcp-server"
],
"env": {
"MAILBUTTONS_API_KEY": "your-value",
"MAILBUTTONS_API_URL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http mailbuttons https://mailbuttons.com/api/v1/mcp/rpc --header 'Authorization: your-value'claude mcp add mailbuttons --env MAILBUTTONS_API_KEY=your-value --env MAILBUTTONS_API_URL=your-value -- npx -y @mailbuttons/mcp-server运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"mailbuttons": {
"url": "https://mailbuttons.com/api/v1/mcp/rpc",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"mailbuttons": {
"command": "npx",
"args": [
"-y",
"@mailbuttons/mcp-server"
],
"env": {
"MAILBUTTONS_API_KEY": "your-value",
"MAILBUTTONS_API_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"mailbuttons": {
"type": "http",
"url": "https://mailbuttons.com/api/v1/mcp/rpc",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"mailbuttons": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mailbuttons/mcp-server"
],
"env": {
"MAILBUTTONS_API_KEY": "your-value",
"MAILBUTTONS_API_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
MAILBUTTONS_API_URL envAuthorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 mailbuttons.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:MAILBUTTONS_API_KEY, Authorization
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.1.4)于9天前进入注册中心。
支持 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、图片和脚本已被移除。链接会离开本站。
The Model Context Protocol server for Mailbuttons, governed email for AI agents. Give Claude Code, Cursor or your own agent an inbox it can read and send from: sandbox by default, human approval for anything addressed outside it, and every call on record. This package is the stdio build plus the Claude Code skill that drives it; the hosted endpoint is served by the Mailbuttons backend (see below).
Mailbuttons runs the agents in its catalogue on this same platform. This server is the way to build your own agent on it.
Get started: sign up and create an API key at
[mailbuttons.com](https://mailbuttons.com) — docs at
Remote MCP endpoint: the production, network-facing MCP server is served
natively by the Mailbuttons backend (Rust/Axum) at
POST /api/v1/mcp/rpc— one
binary, sharing the governance spine directly. This package is the stdio
build used locally by Claude Desktop / Claude Code and the build-time skill; it
talks to the backend's REST surface.
This server is sandbox-by-default and never lets an agent expand its own authority:
send_external, promotes sandbox → production, or adds an inbox. Escalation is only ever a *request* for human approval.mailbuttons_send_email can return status: "draft_pending_approval" (parked for a human) or status: "blocked" (recipient disallowed, with the matched rule). These are expected, normal outcomes — not errors. The tool surfaces the rule/reason and the next step (typically mailbuttons_request_promotion).mailbuttons_audit_tail.| Tool | Capability | Notes |
|---|---|---|
mailbuttons_list_messages | read | List delivered messages in an inbox |
mailbuttons_get_message | read | Full body + attachment metadata |
mailbuttons_get_thread | read | All messages in a thread |
mailbuttons_get_attachment_text | attachments | text/* and CSV inline; PDF not yet supported |
mailbuttons_send_email | send_internal | Governed send/reply; may draft or block |
mailbuttons_list_drafts | read | List sends held for human approval |
mailbuttons_get_draft | read | Fetch one held draft in full |
mailbuttons_extract_code | read | OTP/verification code from allowlisted senders only |
mailbuttons_propose_sender | propose_policy | File an allowlist request (human approval) |
mailbuttons_request_promotion | — | File a capability/promotion request (human approval) |
mailbuttons_audit_tail | — | Read recent governed tool calls |
mailbuttons_export_audit | siem_export flag | Export the audit log as JSONL or CEF |
These twelve tools are the governed runtime surface. They are identical on the hosted endpoint and in this package.
The stdio build adds three helpers for setting an integration up. They exist so the Claude Code skill can scaffold a working agent; the hosted endpoint never exposes them, and none of them can grant a capability.
| Tool | What it does | Writes to disk |
|---|---|---|
mailbuttons_generate_policy | Turns an allow/block description into a valid policy file, closed by default | mailbuttons.policy.json in the current directory |
mailbuttons_scaffold_integration | Writes a governed send wrapper and an inbound webhook handler for your stack | ./mailbuttons/ (or the outDir you pass) |
mailbuttons_run_selftest | Sends one internal test message, waits for it, reads it back, reports pass/fail per stage | nothing |
Both writers only touch the paths named above, inside the directory the server was launched from. Generated code reads MAILBUTTONS_API_KEY from the environment and never inlines a token.
# 1. Email yourself a sign-in code
curl -s -X POST https://mailbuttons.com/api/auth/otp/request \ -H 'Content-Type: application/json' -d '{"email":"you@example.com"}'
curl -s -X POST https://mailbuttons.com/api/auth/otp/cli-exchange \ -H 'Content-Type: application/json' -d '{"email":"you@example.com","code":"123456"}'
curl -s -X POST https://mailbuttons.com/api/v1/mcp/sandbox-inboxes \ -H 'Authorization: Bearer mbk_...' -H 'Content-Type: application/json' -d '{"label":"my agent"}'
Sandbox tokens can read and send within the sandbox domain; anything addressed outside it becomes a draft a human approves. More: https://mailbuttons.com/developers/#mcp
claude mcp add --transport http mailbuttons https://mailbuttons.com/api/v1/mcp/rpc \
--header "Authorization: Bearer mb_sandbox_..."
Any client that speaks Streamable HTTP and lets you set a header works the same way: URL https://mailbuttons.com/api/v1/mcp/rpc, header Authorization: Bearer mb_sandbox_....
{
"mcpServers": { "mailbuttons": { "command": "npx", "args": ["-y", "@mailbuttons/mcp-server"], "env": { "MAILBUTTONS_API_KEY": "mb_sandbox_..." } } } }
| Env var | Default | Description |
|---|---|---|
MAILBUTTONS_API_URL | https://mailbuttons.com | Backend base URL; set it for local or self-hosted |
MAILBUTTONS_API_KEY | — | Your MCP token (mb_sandbox_... or mb_production_...) |
The token is read from the environment only — never hard-code it.
npm run build # tsc -> dist/
npm run lint # tsc --noEmit npm test # build + vitest (includes the version-alignment check)
Releases: bump the version in package.json, server.json (both places), src/server.ts and skill/SKILL.md together; npm test fails if they drift. Then npm publish, then mcp-publisher publish from this directory. See docs/mcp-publishing.md in the monorepo.
MIT. Mailbuttons is a trading name of Code Cutter Limited (UK).