Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
Transactional email and agent mailboxes: send, broadcasts, domains, Correio inboxes.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
MEPMAIL_API_KEY, MEPMAIL_MAIL_TOKEN标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.mepmail.dev/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"mepmail": {
"command": "npx",
"args": [
"-y",
"@mepmail/mcp"
],
"env": {
"MEPMAIL_API_KEY": "your-value",
"MEPMAIL_MAIL_TOKEN": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http mepmail https://api.mepmail.dev/mcpclaude mcp add mepmail --env MEPMAIL_API_KEY=your-value --env MEPMAIL_MAIL_TOKEN=your-value -- npx -y @mepmail/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"mepmail": {
"url": "https://api.mepmail.dev/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"mepmail": {
"command": "npx",
"args": [
"-y",
"@mepmail/mcp"
],
"env": {
"MEPMAIL_API_KEY": "your-value",
"MEPMAIL_MAIL_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"mepmail": {
"type": "http",
"url": "https://api.mepmail.dev/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"mepmail": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mepmail/mcp"
],
"env": {
"MEPMAIL_API_KEY": "your-value",
"MEPMAIL_MAIL_TOKEN": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.mepmail.dev/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 JE4NVRG 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 483 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:MEPMAIL_API_KEY, MEPMAIL_MAIL_TOKEN
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.71.1)于22天前进入注册中心。
支持 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、图片和脚本已被移除。链接会离开本站。
Official MepMail MCP server for local MCP clients — Claude Desktop, Claude Code, Cursor, Codex and anything that speaks stdio. It drives your MepMail instance over the public REST API (Resend-compatible wire) with a team API key, and, with a Correio agent key, your mailboxes: read the inbox, save replies as drafts and send them (or ask the owner to approve).
MepMail also runs a hosted MCP server (OAuth, no install) at https://api.mepmail.dev/mcp. This package is for clients that launch local servers from config. Tool names and result shapes match the hosted server's; it covers a subset — the reading, sending and contact tools (22) — and the write surfaces beyond contacts (segments, topics, broadcasts, templates, webhooks, domains, API keys) plus the team picker are hosted-only.
Guide: https://docs.mepmail.dev/mcp · Packages: https://docs.mepmail.dev/packages · Published as @mepmail/mcp on npm.
Requires Node.js 20 or newer.
/emails, so it would 403 on the contact tools (list_contacts, get_contact, create_contact, update_contact, delete_contact) with restricted_api_key.Claude Desktop (claude_desktop_config.json) — and any client with the same config shape (Cursor: mcp.json):
{
"mcpServers": { "mepmail": { "command": "npx", "args": ["-y", "@mepmail/mcp"], "env": { "MEPMAIL_API_KEY": "ms_...", "MEPMAIL_BASE_URL": "https://api.mepmail.dev" } } } }
Claude Code:
claude mcp add mepmail -e MEPMAIL_API_KEY=ms_... -e MEPMAIL_BASE_URL=https://api.mepmail.dev -- npx -y @mepmail/mcp
Correio mailboxes — create an agent key in Correio → Settings → Agents: mmb_... for one mailbox, or "Connect an agent to several mailboxes" for an mmt_... credential over the mailboxes you choose, with read, draft and optionally send permission. Then add it to the same server (an API key is optional when you only need mailboxes):
claude mcp add mepmail -e MEPMAIL_MAIL_TOKEN=mmt_... -- npx -y @mepmail/mcp
Set at least one of MEPMAIL_API_KEY and MEPMAIL_MAIL_TOKEN.
| Variable | Required | Default | Meaning |
|---|---|---|---|
MEPMAIL_API_KEY | for sending tools | — | Team API key (ms_...). Sent as Bearer to your instance only. |
MEPMAIL_BASE_URL | no | https://api.mepmail.dev | Your instance's API URL. |
MEPMAIL_MAIL_TOKEN | for mailbox tools | — | Correio agent key (mmb_... or mmt_...). Sent as Bearer to the dashboard origin only. |
MEPMAIL_MAIL_ORIGIN | no | https://mepmail.dev | Where your dashboard answers. |
Send and manage email:
send_email — send or schedule one transactional email (cc/bcc/reply_to, tags, attachments, topic-scoped sends).send_email_batch — up to 100 emails in one call.get_email, list_emails — status and timeline (last_event: delivered, bounced, complained, ...).update_email, cancel_email — reschedule or cancel a scheduled email.get_email_insights — per-email best-practice report and score.get_deliverability, get_usage — account standing before bulk work.Audience and account:
create_contact, update_contact, delete_contact (with erase=true for GDPR/LGPD scrubbing), get_contact, list_contacts — with segment filters.list_domains, get_domain — DNS records and verification state.list_broadcasts, get_broadcast.list_templates, get_template.list_webhooks, list_suppressions.Correio mailboxes (with MEPMAIL_MAIL_TOKEN, same five tools as the hosted https://api.mepmail.dev/mcp/correio):
mailbox_list_accounts — the mailboxes the key reaches, with permissions and the default one.mailbox_list_messages, mailbox_read_message — inbox, drafts and sent; pass mailbox with a team credential. Listing is one page at a time, newest first: pass the returned nextCursor as cursor until hasMore is false (a cursor only works for the same mailbox, folder and filters). Filters run on the server before the page is cut: query (words, "quoted phrases", de:/from:, para:/to:, assunto:/subject:, tem:anexo, depois:/antes:), from, subject, unread, after, before; limit up to 100 (50 when searching). Mail that arrives while paging comes before the first page, so start over to see it. A short or empty page never proves a message is absent from the mailbox, and search reads an index that can lag about a minute behind new mail. Dates: a listing's after/before use the order time (arrival, or when a snoozed message came back; a draft's last edit), a search uses the arrival time, and a search also finds snoozed messages, which the listing leaves out until they return.mailbox_get_attachment — one attachment by message id, revision and index (from mailbox_read_message): filename, bytes and sha256. With MEPMAIL_MAIL_DOWNLOAD_DIR set the file is saved there (never overwriting); otherwise it comes back as content_base64, up to 512 KiB.mailbox_save_draft — new draft, edit, reply or forward, from that mailbox's address and signature. attachments adds files as { filename, content_base64 }, or { path } for a file inside MEPMAIL_MAIL_UPLOAD_DIR (no other local path is ever read); keep_attachments picks the files to keep from the edited draft or the forwarded message (by default all of them; a reply keeps none). Limits: 10 files, 256 KiB each, about 700 KiB in all. Files travel only inside the draft request, so nothing is left behind when a draft is abandoned.mailbox_send_draft — sends with the send permission; otherwise the owner gets an approval request (awaiting_approval).Every tool result is one JSON block envelope — { notice, untrusted_data } — so agents can tell team-authored strings from tool output and never treat recipient data as instructions.
send_email and send_email_batch accept an optional top-level idempotency_key. Keep the same key and identical arguments when retrying the same send operation. Generate a new key for a new operation. The server passes it as the HTTP Idempotency-Key header; it is not an email header or message field.
Keys are scoped to the team and retained for 24 hours. A completed retry replays the original result. Reusing a key with different arguments returns a conflict; an operation still in progress can also return a conflict. An incomplete reservation can be recovered after 10 minutes. These limits apply to the server, so use an API version that supports this contract.
MIT