All updates

Support for AI Catalog and MCP Server Card

MCP clients can now find and configure the Resend MCP server from a single URL.

Diel Duarte

Adding an MCP server to a client usually means digging through docs for the right endpoint, transport, and auth setup. Resend now publishes an AI Catalog and an MCP Server Card, so supporting clients can discover the Resend MCP server from just a URL.

How discovery works

Both files are public, static JSON documents any client can read before connecting:

  • AI Catalog at resend.com/.well-known/ai-catalog.json lists the AI artifacts Resend offers, including the remote MCP server.
  • MCP Server Card at mcp.resend.com/mcp/server-card describes the server's name, Streamable HTTP endpoint, and supported protocol versions.

Give a client that supports these discovery methods resend.com, and it reads the AI Catalog, follows the entry to the Server Card, and connects. You still sign in with OAuth, or pass a Resend API key as a Bearer token for headless setups.

Built on open standards

The AI Catalog format is maintained by the Agent Card Working Group under the Linux Foundation. MCP Server Cards are defined in SEP-2127, an official MCP extension.

Get started

If your client supports Server Card discovery, add resend.com as an MCP server and follow the sign-in prompt. For every other client, the server is hosted at https://mcp.resend.com/mcp.

For more installation options, see the MCP server documentation.