# Resend adds AI Catalog and MCP Server Card for MCP server discovery

published: 2026-10-26T18:05:48.637Z
topic: mcp
source: https://resend.com/changelog/ai-catalog-mcp-server-card
url: https://aiagentnews.io/stories/resend-adds-ai-catalog-and-mcp-server-card-for-mcp-server-discovery

Resend now publishes an AI Catalog and an MCP Server Card, so MCP clients that support discovery can find its MCP server from the resend.com domain alone. Clients without discovery support can still connect to the server at its direct endpoint.

Resend publishes two public, static JSON files that clients can read before connecting. The AI Catalog at resend.com/.well-known/ai-catalog.json lists Resend's AI artifacts, including the remote MCP server. The MCP Server Card at mcp.resend.com/mcp/server-card describes the server's name, its Streamable HTTP endpoint and the protocol versions it supports.

A client that supports these discovery methods reads the catalog, follows the entry to the Server Card and connects, starting from resend.com. Sign-in still uses OAuth, and headless setups can pass a Resend API key as a Bearer token.

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. Clients without discovery support can use https://mcp.resend.com/mcp directly.

## Why it matters if you build agents

Agent builders whose MCP clients support these files can add Resend by URL, without looking up the endpoint, transport and auth settings by hand. Clients that do not support discovery still need the direct endpoint, so a manual configuration path remains necessary. Headless agents can keep authenticating with a Resend API key sent as a Bearer token.