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.
Skills that pair with Resend Email
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Build and send HTML email templates with React components, including layout and content elements, Tailwind styling, local preview, and the embeddable visual editor. Use for transactional email, newsletters, password resets, and order confirmations.
Use the Resend API to send transactional or batch email and manage inbound email, templates, domains, contacts, broadcasts, webhooks, API keys, inboxes, automations, delivery events, and account limits. Use whenever a task mentions Resend.
Command-line control of the Resend platform. It sends email, including React Email .tsx templates through --react-email, and manages domains, contacts, broadcasts, templates, webhooks, API keys, logs, automations and events with the `resend` CLI. Load it before any `resend` command, since it documents the non-interactive flags and the pitfalls that otherwise fail silently; it suits shell use, scripts and CI/CD pipelines.
No skills found
Try a different search term or clear the filters.
Local stdio server
Set RESEND_API_KEY and the sender email in the client environment.
npx -y resend-mcpFollow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
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.
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.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
resend-emailappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Send a test email during development. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
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.
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.
Before you connect
- 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.
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.
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