Standard · Converse
MCP server cards
A JSON file that describes a remote MCP server before anyone connects.
Emerging
What it is
A server card is a small file that lists a remote server’s transports, versions and tools, so a client or registry can learn what is there without connecting.
An analogy
The sign outside a shop that lists opening hours and what it sells.
At a glance
- Owner
- MCP project (SEP-2127)
- Maturity
- Emerging Reported final on 2026-10-06; the primary page has not been confirmed. Served at /.well-known/mcp/server-card.json.
- Where it lives
- MCP project
- Framework domain
- Converse: Be asked
- What it serves
- Make your MCP server discoverable
- Say what it supports before a connection
Who should care
The roles this standard touches most. See all the roles on the personas page.
- Engineering and product. Build the access, data, endpoints and actions that agents use, on open standards.
How to adopt it
- 1
Publish the card at /.well-known/mcp/server-card.json.
- 2
Keep its tool list in step with the server.
- 3
Check it against the final schema before you rely on it.
The Institute’s view
Adopt with care
A sensible small file. Because its final status is reported rather than confirmed, check the schema before you invest in tooling around it.
Standards change fast. Last reviewed November 2026.