MCP server cards: make your product callable by agents

The Model Context Protocol (MCP) lets AI clients discover tools your service exposes. A server card is JSON at:

https://yoursite.com/.well-known/mcp/server-card.json

Agents read this file to learn your MCP endpoint, authentication, and available tools.

What to include

• Server name & description — what agents can accomplish.
• Transport — usually HTTP stream to your /mcp (or hosted) endpoint.
• Authentication — Bearer tokens, OAuth, or public read tools.
• Tool list — names, descriptions, and input schemas (or link to full catalog).

Follow the MCP server card schema and test with Cursor, Claude Desktop, or your own client.

Relationship to AI Agent Pages

• Site type Built for AI agents (agent_native) scores MCP and related discovery checks fully.
• SaaS with only docs/API may use Software or API (product) until MCP is live.
• List your live site on AI Agent Pages so directory agents can find you via search_listings and get_listing_spec.

Checklist

1. Deploy a working MCP endpoint.
2. Publish /.well-known/mcp/server-card.json on the same origin (or document the canonical URL in llms.txt).
3. Verify with an MCP inspector or our readiness scan.
4. Submit or update your directory listing.

See also

• llms.txt guide
• Connect your agent to the AI Agent Pages MCP server (dogfood pattern)
• Agent Tool Finder