
This article is part of The MCP Guide. For the month in review, see our State of MCP reports.
An MCP Server Card is a small JSON document that tells an AI app where your remote MCP server lives and how to connect, before it connects. SEP-2127, "MCP Server Cards - HTTP Server Discovery", reached Final status and was merged on 6 October 2026, according to its pull request.
The proposal is Final, but the extension is not finished. Under the extension lifecycle adopted in late October, the extensions overview lists Server Cards as "Beta, destination not yet stated." Expect real usage and possible breaking changes.
Checked against: SEP-2127, the ext-server-card repository (README, schema.json, examples and discovery doc) and the extensions overview on 2 November 2026.
Key Takeaways
- A Server Card describes a remote MCP server's identity and connection details so clients can find and configure it without connecting first.
- Only four fields are required:
$schema,name,versionanddescription; remote endpoints go in an optionalremoteslist. - Domains can list their servers in an AI Catalog at
/.well-known/ai-catalog.json, and cards themselves are recommended at<streamable-http-url>/server-card. - Cards deliberately leave out tools, resources and prompts, because those can differ by user and session.
- SEP-2127 is Final, but the extension is classified Beta with no stated destination as of 2 November 2026.
The problem Server Cards solve
Today, someone usually pastes a server URL into a config file by hand. The spec's server/discover method only helps once you already know where to connect. SEP-2127 lists the pain points: manual endpoint setup, "no domain-level discovery," and no metadata available without a live connection.
Server Cards fill that gap with static, cacheable metadata. SEP-2127 names three uses:
- Autoconfiguration. An IDE pointed at a domain can set itself up.
- Automated discovery. Clients and registries can crawl domains and index servers.
- Lower latency. Apps can show server details without opening each endpoint.
What a Server Card contains
The schema in the extension repository requires four fields and allows six more.
| Field | Required | What it holds |
|---|---|---|
$schema | Yes | The schema URL, e.g. https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json |
name | Yes | A unique name in reverse DNS style, such as com.example/weather |
version | Yes | The server version |
description | Yes | What the server does |
title | No | A human-friendly name |
icons | No | Icons with src and optional size, type and theme |
repository | No | Source code location |
websiteUrl | No | Product or docs page |
remotes | No | Endpoints: type, url, optional headers, variables and supportedProtocolVersions |
_meta | No | Namespaced vendor data |
The smallest valid card in the repository's examples is just this:
{
"$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
"name": "example-org/minimal",
"version": "1.0.0",
"description": "Smallest valid Server Card."
}
A fuller example adds a streamable-http remote with a templated URL such as https://{tenant}.example.com/mcp, an Authorization header marked as secret, and supported protocol versions. Header values can use variables, so a card can say "a bearer token goes here" without ever containing one.
How clients find cards: the AI Catalog
Server Cards do not define their own well-known path. Instead, the discovery doc uses an AI Catalog, a JSON file an organization publishes to list its AI artifacts.
For domain-level discovery, a host may publish the catalog at /.well-known/ai-catalog.json. Each MCP entry has an identifier, a type of application/mcp-server-card+json, and either a url pointing to the card or the card inline as data.
The client flow is:
- Fetch
https://{domain}/.well-known/ai-catalog.json. - Pick entries whose type is the MCP Server Card media type.
- Fetch each card from its URL, or read it inline.
- Use the card to configure and open an MCP connection.
A catalog can point to cards on other domains. SEP-2127's example is a restaurant whose catalog lists one card hosted by a reservations platform and another hosted by a jobs platform.
What Server Cards leave out, on purpose
Cards do not list tools, resources or prompts. SEP-2127 explains that "MCP servers are inherently dynamic": what a server exposes can vary by user, session, configuration and feature flags. Clients still call tools/list and similar methods after connecting.
Cards also do not advertise capabilities or extension support. They give supportedProtocolVersions so a client knows whether to try. If a card and the live server disagree, SEP-2127 says clients "SHOULD prefer the live server/discover values."
Server Cards vs the MCP Registry's server.json
The two formats serve different jobs. A Server Card describes "remote MCP connectivity only." The MCP Registry's server.json also covers local packages, install commands and environment variables, and the Registry owns that schema. Where the formats overlap, they use compatible field names. Our MCP Registry explainer covers server.json, and you can check one with our server.json validator.
Security notes
SEP-2127 treats cards as public, read-only documents:
- Servers "MUST NOT include credentials, internal network topology, proprietary logic, or user/session-specific data."
- Wide-open CORS is acceptable because the content is public.
- Cards SHOULD be served over HTTPS, and a tampered card mainly harms discoverability because clients verify against the live server.
- Servers SHOULD rate-limit discovery endpoints, and clients SHOULD respect cache headers.
Leaving tools out is also a safety feature. A client cannot rely on a static manifest for access decisions. Our MCP security checklist covers the runtime checks that still apply.
Status and support as of November 2026
- SEP: Final, merged 6 October 2026, Extensions Track.
- Lifecycle stage: Beta, destination not yet stated, per the extensions overview.
- Repository: renamed from
experimental-ext-server-cardtoext-server-card. On 2 November 2026 its README still said "Status: Experimental," which predates the Beta classification. - Implementations: SEP-2127 lists an experimental Python SDK pull request, an experimental Go SDK pull request and a Goose demo. We did not find Server Cards in the client support matrix.
Next step
If you run a public remote MCP server, publishing a Server Card and an AI Catalog entry is a low-cost way to be found by crawlers and registries as support grows. Our MCP marketing team handles listings and discovery, and our MCP development team can add a card to your server.
More in the MCP Guide
Latest research: State of MCP: October 2026
Frequently asked questions
What is an MCP Server Card?
It is a JSON document, with media type application/mcp-server-card+json, that describes a remote MCP server's name, version, description and connection endpoints. Clients can read it before connecting, which supports autoconfiguration and discovery by domain.
Where should I host my Server Card?
Cards can live at any unreserved URL. SEP-2127 reserves <streamable-http-url>/server-card as the recommended location. For domain-level discovery, list the card in an AI Catalog at /.well-known/ai-catalog.json.
Does a Server Card list my server's tools?
No. Cards intentionally leave out tools, resources and prompts, because those can change by user, session and configuration. Clients still list them at runtime after connecting.
Are Server Cards final?
The proposal, SEP-2127, is Final. The extension itself is at the Beta stage under SEP-3392, with no stated destination as of 2 November 2026, so the format can still change.
Do Server Cards replace server.json in the MCP Registry?
No. A Server Card covers remote connectivity only. The Registry's server.json also describes local packages and install details. The two use compatible fields where they overlap.











