Resend Lets AI Clients Find Its MCP Server From One URL

Resend now publishes an AI Catalog and an MCP Server Card, so an MCP client that supports them can find and configure the Resend MCP server from the address resend.com alone, the company said in an Oct. 26 changelog entry. Resend said adding an MCP server to a client usually means digging through docs for the endpoint, transport and auth setup.

Two public JSON files do the work

Both files are static documents any client can read before it connects, according to Resend. The AI Catalog sits at resend.com/.well-known/ai-catalog.json and lists the AI artifacts Resend offers, including the remote MCP server. The MCP Server Card sits at mcp.resend.com/mcp/server-card and describes the server’s name, its Streamable HTTP endpoint and the protocol versions it supports.

We checked both files on Oct. 28. The catalog has one entry, which points to the Server Card. The card lists version 1.2.2 of the com.resend/mcp server, the endpoint https://mcp.resend.com/mcp and six supported protocol versions, the newest dated 2026-07-28.

A client follows the catalog to the card

Resend said a client that supports these discovery methods reads the catalog, follows the entry to the card and connects. Sign-in is unchanged. Authenticate with OAuth, or pass a Resend API key as a Bearer token for headless setups.

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

Key takeaways

• Resend publishes an AI Catalog and an MCP Server Card as public JSON.
• A supporting client needs only resend.com to find the MCP server.
• OAuth or a Bearer API key is still required to connect.

The take

We think the gain is one less copy-and-paste step. A client that reads a server’s address, transport and protocol versions from a file never asks anyone to copy them from a docs page. Copied settings go stale when the server moves.

Client support is the limit. Resend says “supporting clients,” and the standards behind both files are new. Clients without them still need a hand-written config.

Teams building agents on email should check whether their client reads Server Cards. If it does, point it at resend.com and see whether it connects without a hand-written config.