Resend's remote MCP server now supports the stateless protocol.
The MCP specification just released a major upgrade, and now Resend's remote MCP server supports this latest version.
No changes required. If you are already using the Resend MCP server, or if you install it today, you should see no change.
The new specification is the largest revision of the protocol since the initial launch of MCP. It includes several changes, including:
Several of these changes make it easier to scale remote MCP servers. Without a protocol defined session, requests can flow to any MCP server instance. Previously, with OAuth 2.0 Dynamic Client Registration (DCR), every client installation created a new registration that the remote server had to retain, allowing stored state to grow without limit.
The replacement for DCR is Client ID Metadata Documents (CIMD). Instead of registering at runtime, the client hosts a JSON document that Resend fetches during authorization, so there's no registration call. The process gives the client a stable identity whether it's a hosted app, a CLI, or an MCP server. This applies to any OAuth client against Resend, not only MCP. View more guidance on how to create an OAuth Client for Resend.
The update is backwards compatible so older MCP clients and updated MCP clients continue to work.
If your client implements the new spec, it will automatically switch over, while older clients will still be able to use the previous version.
If you haven't connected your agent with the remote Resend MCP server yet you can install it with any of the following options.
Connect Resend from the connector directory. The Connector bundles the MCP server and every Resend skill.
If your client isn't shown here, the server is hosted at https://mcp.resend.com/mcp. For more installation options, see the MCP server documentation.
Want to see what you can do with the MCP server? Check out this short video: