---
title: "Remote MCP Supports the 2026-07-28 Spec"
slug: resend-mcp-supports-the-new-2026-07-28-spec
description: "Resend's remote MCP server now supports the stateless protocol."
created_at: "2026-08-06"
updated_at: "2026-08-06"
image: "https://cdn.resend.com/posts/resend-mcp-supports-the-new-2026-07-28-spec.jpg"
humans: ["diel-duarte", "gabriel-miranda", "felipe-freitag"]
---

The [MCP specification just released a major upgrade](https://blog.modelcontextprotocol.io/posts/2026-07-28/), and now Resend's remote MCP server supports this latest version.

## What should you change?

**No changes required**. If you are already using the Resend MCP server, or if you [install it today](#install-the-remote-mcp-server), you should see no change.

## What's new about the spec?

The [new specification](https://blog.modelcontextprotocol.io/posts/2026-07-28/) is the largest revision of the protocol since the initial launch of MCP. It includes several changes, including:

- **A stateless core** that scales on ordinary HTTP infrastructure
- **First-class extension support** including MCP Apps and task extensions
- **Authorization improvements** to align with OAuth and OpenID Connect deployments
- **A formal deprecation policy** so the protocol can evolve without disruption

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.

<Callout type="insight">
The replacement for DCR is [Client ID Metadata Documents](https://datatracker.ietf.org/doc/draft-ietf-oauth-client-id-metadata-document/) (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](/docs/guides/building-a-resend-oauth-client).
</Callout>

## Backwards compatibility

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.

## Install the remote MCP server

If you haven't connected your agent with the remote Resend MCP server yet you can install it with any of the following options.

<Tabs>

<Tab label="Claude">

Connect Resend from the [connector directory](https://claude.ai/directory/connectors/resend). The Connector bundles the MCP server and every Resend skill.

</Tab>

<Tab label="Claude Code">

```bash copy
claude plugin install resend@claude-plugins-official
```

The plugin bundles the MCP server and every Resend skill.

</Tab>

<Tab label="Cursor">

Open the command palette and choose **Cursor Settings** > **Tools & MCPs** > **Add Custom MCP**.

```json copy
{
  "mcpServers": {
    "resend": {
      "url": "https://mcp.resend.com/mcp"
    }
  }
}
```

</Tab>

<Tab label="Codex">

Install the [Resend plugin](https://chatgpt.com/plugins/plugin_asdk_app_6a3c407853888191beddc2151c2b6f8b?open_in_codex) in one click. It bundles the MCP server and every Resend skill.

</Tab>

<Tab label="Codex CLI">

```bash copy
codex mcp add resend --url https://mcp.resend.com/mcp
```

</Tab>

<Tab label="Warp">

In Warp's Settings, navigate to **Agents** > **MCP servers**, and click **+ Add** to add a new server.

```json copy
{
  "resend": {
    "serverUrl": "https://mcp.resend.com/mcp"
  }
}
```

</Tab>
</Tabs>

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](https://resend.com/docs/mcp-server).

Want to see what you can do with the MCP server? Check out this short video:

<YouTube videoId="GjLb4hFo2qg" />