---
title: "Support for AI Catalog and MCP Server Card"
slug: ai-catalog-mcp-server-card
description: "MCP clients can now find and configure the Resend MCP server from a single URL."
created_at: "2026-10-26"
image: https://cdn.resend.com/posts/mcp-server-card.jpg
humans: ["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.

<video
  src="https://cdn.resend.com/posts/ai-catalog-mcp-server-card.mp4"
  autoPlay
  loop
  muted
  playsInline
  className="extraWidth"
/>

## Built on open standards

The [AI Catalog](https://ai-catalog.io/) format is maintained by the Agent Card Working Group under the Linux Foundation. MCP Server Cards are defined in [SEP-2127](https://modelcontextprotocol.io/seps/2127-mcp-server-cards), 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](https://resend.com/docs/mcp-server).