
Resend Mcp Server
io.github.friendlygeorge由 GitHub 账号 friendlygeorge 发布v1.0.0更新于 Oct 24, 2026
MCP server for Resend — transactional email API for AI assistants...
概览
一个本地 MCP 服务器,将 AI 助手连接到 Resend 事务邮件 API,用于发送邮件并管理域名、API 密钥、受众和联系人。
- 可以做什么
- 发送单封或批量事务邮件(每次最多 100 封),并列出或查看已发送邮件及其投递状态。创建、列出、验证和删除发信域名。创建、列出和删除 API 密钥。列出和创建受众,并在受众中列出、查看、创建、更新和删除联系人。
- 适用场景
- 适合让助手在对话中处理事务邮件:欢迎邮件、收据、通知、向受众发送简报,或在不打开控制台的情况下审计和清理 Resend 的域名、密钥与联系人。
- 运行要求
- 通过 npx 以 npm 包形式在本地运行,需要 Node.js 18+ 和 npm。需要 Resend 账户和 API 密钥,通过环境变量 RESEND_API_KEY 提供。需要访问 Resend API 的网络连接。
安装
在 SourceWeft 中
- 打开 控制台中的 Resend Mcp Server,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Resend MCP Server
An MCP server for Resend — connect any MCP-compatible client to the Resend transactional email API.
[npm version] [npm downloads] [License: MIT] [MCP Compatible] [TypeScript] [Claude Desktop] [Cursor]
What is this?
An MCP (Model Context Protocol) server that gives AI assistants and agents full access to Resend's email API — send single or batch emails, manage sending domains, API keys, audiences, and contacts — through natural language.
Use it with Claude Desktop, Cursor, Windsurf, Cline, Continue, or any MCP-compatible client to send emails, manage infrastructure, and build automation around email.
Why use this?
- 18 built-in tools — covers sending (single + batch), domains, API keys, audiences, and contacts
- Send emails by talking — "send a welcome email to [email protected]" just works
- Manage your infrastructure — create/verify/delete domains, mint/revoke API keys, manage contacts
- Batch sending — send up to 100 emails in a single API call
- Full contact CRUD — create, read, update, and delete contacts across audiences
- Rate-limited automatically — respects Resend's 10 req/s free tier, retries on 429
- Works with every MCP client — Claude Desktop, Cursor, Windsurf, Cline, Continue, and more
Quick Start
Add to your MCP client config (e.g. claude_desktop_config.json):
Get a free API key at resend.com/api-keys.
Use it
Ask your AI assistant things like:
- "Send an email to [email protected] thanking her for signing up"
- "List the last 5 emails I sent"
- "What happened to email ID
abc-123?" - "Create a new sending domain for
mail.acme.com" - "Verify domain
domain-xyz" - "Mint a new API key called 'production-server'"
- "Add [email protected] to audience
audience-1"
Tools
Use Cases
Transactional Email Automation
"Send a welcome email to every new signup" — automate onboarding flows, receipts, and notifications through natural language. No more switching between email dashboards.
Domain Management
"Add mail.acme.com as a sending domain and verify it" — manage DNS records, DKIM, and SPF through your AI assistant instead of logging into Resend's dashboard.
Contact & Audience Management
"Add [email protected] to my VIP audience" — build and segment contact lists without touching a spreadsheet. Full CRUD on contacts and audiences.
Batch Campaigns
"Send this newsletter to all contacts in audience-1" — batch-send up to 100 emails in one call. Perfect for newsletters, product announcements, or re-engagement campaigns.
Infrastructure Audit
"List all my API keys and domains" — audit your Resend setup in seconds. See which keys are active, which domains are verified, and clean up stale resources.
Security
- API key required — Resend API key is passed via environment variable, never logged or stored in files.
- No local file access — does not read or write any files on your machine.
- No shell access — does not execute commands or spawn processes.
- Rate-limited — automatically caps requests at ~9 req/s to stay within Resend's free tier.
- Open source — MIT licensed. Inspect the code at GitHub.
Troubleshooting
Rate limit errors (429)
The server auto-retries on 429 with a 2s backoff. Free tier allows 10 req/s. The server caps at ~9 req/s to stay safe. If you hit this frequently, consider upgrading your Resend plan.
"Invalid API key" errors
Verify your RESEND_API_KEY starts with re_ and is active at resend.com/api-keys. Keys take up to 30 seconds to propagate after creation.
Server won't start
Make sure Node.js 18+ is installed: node --version. If using npx, ensure npm is up to date: npm install -g npm@latest.
MCP client can't connect
Verify the config path is correct. Claude Desktop uses ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows. Restart the client after config changes.
Emails not delivering
Check list_emails for delivery status. Common issues: missing DNS records (run verify_domain), bounce due to invalid address, or domain not yet verified. Resend's dashboard shows detailed webhook events.
Requirements
- Node.js 18+
- A Resend account and API key (
RESEND_API_KEY)
Rate Limits
The server automatically rate-limits requests to ~9 calls/second to stay safely under Resend's free-tier limit of 10 req/s. If you hit a 429 anyway, it waits 2s and retries once.
Development
License
MIT
来源:README.md,提交 63b0e86
工具
0版本历史
1- v1.0.0最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分