Resend offers a hosted, MCP server with OAuth authentication built in.
Agents are everywhere, your terminal, browser, and automation tools. We've been hard at work to bring our MCP server to everywhere your agents live.
Today, we're launching our hosted, remote MCP server at mcp.resend.com/mcp with full OAuth support for authentication. Use it with all your agents today.
With the remote MCP server:
Hosting the server enables a single, trusted endpoint for all MCP clients. Streamable HTTP transport works anywhere remote MCP servers are supported.
Go to Settings → Connectors → Add custom connector, and enter:
https://mcp.resend.com/mcp
Our local resend-mcp server stays open source for self-hosting, air-gapped setups, and stdio clients. For all other MCP clients and surfaces, see the MCP server docs.
We've added OAuth authentication to the MCP server, so you can sign in with your Resend account when you connect. Choose your account and grant the necessary permissions.
You can view or revoke your MCP server's OAuth permissions from your Resend account's Team settings.
If your client runs somewhere a browser login isn’t possible (a server, CI, scripts, or a headless agent), pass a Resend API key as a Bearer token instead of using OAuth.
claude mcp add --transport http resend https://mcp.resend.com/mcp --header "Authorization: Bearer re_xxxxxxxxx"
The remote MCP server gives your AI agent native access to the full Resend platform through a single integration: emails, templates, broadcasts, contacts, logs, webhooks, and more.
View a full list of all features and supported clients.
Each logged action includes a user agent trace, so you have full visibility on each logged action your agent takes with MCP.
The remote MCP server opens up a new way to interact with Resend, allowing you to control your email campaigns and contacts from anywhere, to build custom integrations, and more.
The applications are nearly endless and we can't wait to see what you build with it.