Support .well-known server card for MCP server discovery

[matzew]

Summary

The MCP specification's Server Card Working Group is developing .well-known metadata conventions that allow clients to discover and reason about MCP servers without connecting to them first.

The operator is well-positioned to auto-generate or serve .well-known metadata for managed MCP servers, since it already knows the server's capabilities, address, protocol version, and identity from the handshake.

Motivation

From the MCP Roadmap:

Server Card Working Group is developing .well-known metadata conventions, allowing server discovery and reasoning without connecting.

Today, clients must connect to an MCP server and perform a server/discover or initialize handshake to learn what it offers. A .well-known endpoint would let clients (or registries) discover this information passively.

Possible approaches

• Auto-generate a .well-known/mcp.json (or similar) from status.serverInfo after a successful handshake
• Expose server card metadata via an annotation or status field that external tooling (Ingress, gateway) can serve
• Integrate with MCP registries (Integration with Anthropic MCP Registries #179) so the operator can publish server cards on behalf of managed servers

Related

• Integration with Anthropic MCP Registries #179 - Integration with Anthropic MCP Registries
• Umbrella issue: supporting new MCP spec #199 - Umbrella issue: supporting new MCP spec