Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 4
- 4 5
- 3 0
- 2 0
- 1 0
Trust in production
- Trust it - 78%
- With caveats - 22%
- Wouldn't - 0%
100% would recommend this server
How reviewers scored it
- Setup & docs 4.1
- Auth experience 4.3
- Reliability 4.3
- Maintainer responsiveness 4.1
Why it got an A
This grade describes Resend's own open-source server (resend/resend-mcp, MIT, npm resend-mcp). The README says the hosted endpoint at mcp.resend.com runs the same code, and Resend's Claude plugin points at that hosted URL. The hosted server signs in with OAuth by default and accepts an API key as a Bearer header for headless use; the local server takes RESEND_API_KEY over stdio or an HTTP port you start yourself. Dozens of tools cover sending and batch email, scheduling, inbound emails and inboxes, broadcasts, contacts, templates, domains, suppressions, webhooks, logs and API keys. Biggest caution: with a full-access key or a broad OAuth grant the agent can send real email to real people, send broadcasts to a whole segment, delete domains and create or remove API keys. Delete tools tell the model to double-check with you first, but that is an instruction in the tool text, not something your client enforces, and the send tools carry no such line. The server sets no send limit of its own: limits come from your Resend account, and a usage tool reports quota and rate limit. Use a sending-only key restricted to one domain where you can, and keep tool approval on. Releases are near-daily, nine human authors in 90 days, no advisories.
How to connect
Hosted: claude mcp add --transport http resend https://mcp.resend.com/mcp (OAuth). Local: claude mcp add resend -e RESEND_API_KEY=re_xxx -- npx -y resend-mcpIs Resend MCP Server safe?
Is Resend MCP Server safe to use?
Resend MCP Server grades A: all four checks are at full marks. Strong public trust signals. It is still not a full audit, so give it the narrowest access that works.
Does Resend MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Resend MCP Server support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Amplitude MCP ServerAmplitude's hosted MCP server for product analytics - search and query events, charts, dashboards, experiments, feature flags, cohorts and session replay, with OAuth sign-in and a separate EU endpoint.
- A Appwrite MCP ServerOfficial Appwrite server that exposes databases, users, functions, teams and storage as tools, hosted with OAuth or run locally with a project API key.
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Better Stack MCP ServerOfficial hosted Better Stack server to read and manage incidents, monitors, status pages and on-call, and run SQL over your logs, spans and metrics, with OAuth or an API token.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
Embed this badge
[](https://trustedmcp.io/servers/resend-mcp)<a href="https://trustedmcp.io/servers/resend-mcp"><img src="https://trustedmcp.io/badge/resend-mcp.svg" alt="TrustedMCP grade A" height="80"></a>Community reviews
Better than the DIY script it replaced
Simple to set up in Cursor, simple to reason about. You can tell it is actively maintained, the rough edges keep getting fixed. The OAuth flow worked first time in Claude Code. Sign-in flow was painless and I never had to paste a key into a config file.
Used for Keeping project tickets in sync with code changes
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 3/5
The Resend integration I wanted
Been running this for about a month now. You can tell it is actively maintained, the rough edges keep getting fixed. Easy recommendation.
Used for CI failure investigation
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Easy win for our agent setup
Started with it as an experiment, now it is a fixture. Being official from Resend counts for a lot when I pitch it to security. Auth is handled properly, and revoking access later was one click.
Used for Internal developer assistant
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Good defaults, good docs
Installed it on a Friday, it was part of my workflow by Monday. Scoped the token to just what the agent needs and it respected that.
Used for Code review summaries for pull requests
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Set it up once, forgot about it
Clear tool names, sensible outputs, very few surprises. Auth is handled properly, and revoking access later was one click. It is in our production agent and I sleep fine.
Used for Looking up Resend data without leaving the editor
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Surprisingly polished
Our agents call this dozens of times a day. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Keep permissions tight and it is a good tool.
Used for Automating release notes
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Trustworthy enough for real work
Replaced a homegrown script with Resend MCP Server and have not looked back. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. I would use it in prod, but only with a human approving writes.
Used for Scripting routine maintenance tasks
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Quietly reliable
Of the Resend integrations I tried, this one is the most predictable. Releases come often and the changelog is clear. Sign-in flow was painless and I never had to paste a key into a config file. The API key sits in the config file, so I made a dedicated key with minimal permissions.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Clean integration, sensible permissions
I use this almost daily. Sign-in flow was painless and I never had to paste a key into a config file. Updates land regularly, and nothing broke when I upgraded. Gave it its own API key so I can revoke it without breaking anything else. Good choice if you need Resend in your agent.
Used for Debugging sessions in Cursor
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.