Until now, adding a SaaS product to an AI assistant usually meant searching its docs for the right endpoint, transport and auth setup. On October 26, Resend shipped a shortcut: give a supporting client resend.com, and it finds Resend's MCP server, connects and asks you to sign in. (Resend)

It does this with two small, public JSON files:

Is your SaaS agent-ready? Get your score
  • An AI Catalog at resend.com/.well-known/ai-catalog.json, which lists the AI artifacts Resend offers, including its remote MCP server.
  • An MCP Server Card at mcp.resend.com/mcp/server-card, which describes the server's name, its Streamable HTTP endpoint and the protocol versions it supports.

The client reads the catalog, follows it to the card, and connects. Sign-in still goes through OAuth, or through an API key passed as a Bearer token for headless setups.

These are open standards, not a Resend trick

Resend didn't invent a format. According to Resend, the AI Catalog format is maintained by the Agent Card Working Group under the Linux Foundation, and MCP Server Cards are defined in SEP-2127, an official MCP extension. (Resend) Any SaaS company can publish the same two files.

Why this is the new SEO

For twenty years, being findable meant ranking in Google. Now more and more work starts with someone asking an AI assistant to do something, and the assistant reaches for whatever tools it can find and connect to.

Discovery files work for agents the way a sitemap works for search engines. A product that publishes them can be found and connected from its domain name alone. A product that doesn't publish them is invisible until someone digs through its docs.

The cost of being invisible doesn't show up right away. A customer asks their assistant to handle a task. The assistant can do it in a competitor's product and not in yours, so the task moves. Nobody files a cancellation. Usage just slips, and the renewal gets harder. That's ghost churn.

What to check on your own site

  1. Do you have an MCP server at all? Without one, discovery files have nothing to point to.
  2. Can an agent find it from your domain? Publishing an AI Catalog and a Server Card takes a couple of static files.
  3. Can agents read your site? That means an llms.txt file, robots.txt rules that let AI crawlers in, public API docs and structured data.
  4. Is sign-in agent-friendly? Resend still requires OAuth for every connection, and you should too.

See where your product stands

Our free Agent Readiness Check scans your site for the signals AI agents look for and gives you a score in about a minute.

Is your SaaS agent-ready? Get your score

Is your SaaS agent-ready? Get your score

Run a free Pryno readiness check on your MCP server