Hosted MCP server/Communication Official

Official Resend Email MCP server

Hosted at mcp.resend.com·Streamable HTTP

Resend's MCP server sends email from an editor or assistant through the Resend API. The provider documents two paths: a local stdio server, npx -y resend-mcp, configured with RESEND_API_KEY and SENDER_EMAIL_ADDRESS, and a hosted endpoint at https://mcp.resend.com/mcp that requires OAuth. Both use the same Resend account and sending domain.

mcp.resend.com Streamable HTTP OAuth Source checked Oct 31, 2026 Server not checked yet Reviewed 2026-11-16
About

Where it fits

Developers who want to send test or transactional email without leaving their editor.

  • Send a test email during development.
  • Use the local stdio server with a Resend API key.
  • Use the hosted endpoint with OAuth.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

Set RESEND_API_KEY and the sender email in the client environment.

npx -y resend-mcp

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://mcp.resend.com/mcp
Host
mcp.resend.com · /mcp
Transport
Streamable HTTP
Authentication
OAuth
Server name
resend-email
Listing type
Official provider listing

The installer uses the server name resend-email. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that resend-email appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Send a test email during development. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.

Provider page available on Oct 31, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Resend Email documentationhttps://resend.com/docs/mcp-serverGitHub repositoryhttps://github.com/resend/mcp-send-email