Complete Resend email MCP: full API coverage + debug layer (deliverability, DNS, bounces).
If you already use Resend Email MCP, the resend email mcp mcp server is the piece that lets your assistant work with it directly. Complete Resend email MCP: full API coverage + debug layer (deliverability, DNS, bounces).
Works with Claude Code, Cursor, Claude Desktop, and any other MCP client.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Emails — The Emails tool exposed by this serverDomains — The Domains tool exposed by this serverBroadcasts — The Broadcasts tool exposed by this serverContacts — The Contacts tool exposed by this serverSegments — The Segments tool exposed by this serverTemplates — The Templates tool exposed by this serverTopics — The Topics tool exposed by this serverWebhooks — The Webhooks tool exposed by this serverLogs — The Logs tool exposed by this serverresend-email-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: RESEND_API_KEY, RESEND_FROM, RESEND_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Resend Email MCP's toolset — Emails, Domains, Broadcasts and 6 more — is a fair guide to whether it matches your workflow. It is maintained by helbertparanhos; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Emails | The Emails tool exposed by this server. |
| Domains | The Domains tool exposed by this server. |
| Broadcasts | The Broadcasts tool exposed by this server. |
| Contacts | The Contacts tool exposed by this server. |
| Segments | The Segments tool exposed by this server. |
| Templates | The Templates tool exposed by this server. |
| Topics | The Topics tool exposed by this server. |
| Webhooks | The Webhooks tool exposed by this server. |
| Logs | The Logs tool exposed by this server. |
{
"mcpServers": {
"resend-email": {
"command": "npx",
"args": ["-y", "resend-email-mcp"],
"env": {
"RESEND_API_KEY": "your-value",
"RESEND_FROM": "your-value",
"RESEND_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| RESEND_API_KEY | Credential the server authenticates with. | Yes |
| RESEND_FROM | Configuration value read at startup. | Optional |
| RESEND_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.