modelcontextprotocol/ext-server-card
Watch
1
0
Fork
You've already forked ext-server-card
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: align Catalog mediaType with AI Catalog spec

Browse source 
Replace application/mcp-server+json with application/mcp-server-card+json
in docs/discovery.md to match the AI Catalog specification, which
discovery.md cites as the standard MCP Catalog entries are a subset of.

Fixes #9

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Sam Morrow 2026-06-05 22:13:08 +02:00
commit 877e62682c
1 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/discovery.md
View file

@ -54,7 +54,7 @@ Each entry in the `entries` array describes a single MCP server and MUST contain
| :------------ | :----- | :------- | :------------------------------------------------------------------------------- | | :------------ | :----- | :------- | :------------------------------------------------------------------------------- |
| `identifier` | string | Yes | A URN identifying this server (e.g., `urn:mcp:server:com.example/weather`) | | `identifier` | string | Yes | A URN identifying this server (e.g., `urn:mcp:server:com.example/weather`) |
| `displayName` | string | Yes | A human-readable name for the server | | `displayName` | string | Yes | A human-readable name for the server |
| `mediaType` | string | Yes | The media type of the referenced artifact. MUST be `application/mcp-server+json` | | `mediaType` | string | Yes | The media type of the referenced artifact. MUST be `application/mcp-server-card+json` |
| `url` | string | Yes | URL where the full [Server Card](#mcp-server-cards) can be retrieved | | `url` | string | Yes | URL where the full [Server Card](#mcp-server-cards) can be retrieved |
The `identifier` MUST begin with `urn:mcp:server:` and end with the `name` value of the The `identifier` MUST begin with `urn:mcp:server:` and end with the `name` value of the
@ -71,7 +71,7 @@ A domain hosting a single MCP server, using only the required fields:
{ {
"identifier": "urn:mcp:server:com.example/weather", "identifier": "urn:mcp:server:com.example/weather",
"displayName": "Weather Service", "displayName": "Weather Service",
"mediaType": "application/mcp-server+json", "mediaType": "application/mcp-server-card+json",
"url": "https://example.com/.well-known/mcp-server-card" "url": "https://example.com/.well-known/mcp-server-card"
} }
] ]
@ -89,19 +89,19 @@ A domain hosting several MCP servers, each with its own server card:
{ {
"identifier": "urn:mcp:server:com.acme/code-review", "identifier": "urn:mcp:server:com.acme/code-review",
"displayName": "Code Review Assistant", "displayName": "Code Review Assistant",
"mediaType": "application/mcp-server+json", "mediaType": "application/mcp-server-card+json",
"url": "https://acme.com/.well-known/mcp-server-card/code-review" "url": "https://acme.com/.well-known/mcp-server-card/code-review"
}, },
{ {
"identifier": "urn:mcp:server:com.acme/docs-search", "identifier": "urn:mcp:server:com.acme/docs-search",
"displayName": "Documentation Search", "displayName": "Documentation Search",
"mediaType": "application/mcp-server+json", "mediaType": "application/mcp-server-card+json",
"url": "https://acme.com/.well-known/mcp-server-card/docs-search" "url": "https://acme.com/.well-known/mcp-server-card/docs-search"
}, },
{ {
"identifier": "urn:mcp:server:com.acme/ci-cd", "identifier": "urn:mcp:server:com.acme/ci-cd",
"displayName": "CI/CD Pipeline", "displayName": "CI/CD Pipeline",
"mediaType": "application/mcp-server+json", "mediaType": "application/mcp-server-card+json",
"url": "https://acme.com/.well-known/mcp-server-card/ci-cd" "url": "https://acme.com/.well-known/mcp-server-card/ci-cd"
} }
] ]
@ -127,14 +127,14 @@ flowchart TD
3. For each entry, retrieve the server card from the entry's `url` 3. For each entry, retrieve the server card from the entry's `url`
4. Use the server card metadata to configure and establish an MCP connection 4. Use the server card metadata to configure and establish an MCP connection
Clients SHOULD validate that each entry has `mediaType` set to `application/mcp-server+json` Clients SHOULD validate that each entry has `mediaType` set to `application/mcp-server-card+json`
and ignore entries with unrecognized media types. and ignore entries with unrecognized media types.
## MCP Server Cards ## MCP Server Cards
An **MCP Server Card** is a JSON document that describes a single MCP server — its An **MCP Server Card** is a JSON document that describes a single MCP server — its
identity, capabilities, and connection details. Server Cards use the media type identity, capabilities, and connection details. Server Cards use the media type
`application/mcp-server+json`. `application/mcp-server-card+json`.
A Server Card includes: A Server Card includes: