Repository navigation
Include ServerCapabilities in server.json #84
Description
Activity
This could also be formed as server tags/keywords rather than having a strict dependence on capabilities.
It would be nice to have all capabilities mentioned in server.json to list them. A protected MCP server may need auth to even find capabilities eg GitHub MCP
+1 to this ask. Would love to see it prioritised/implemented.
Any progress on this?
Relabeling this as
v1. Most of the substance here is being worked upstream in the spec repo rather than here. The most directly relevant threads:- SEP-2127: MCP Server Cards —
.well-known/mcp/server-card.jsonfor pre-connection capability discovery - SEP-1381: Utilized Capability Declarations
- SEP-1821: Dynamic Tool Discovery
Once those land at the protocol layer, the registry can mirror the same fields in server.json. Keeping this open as the canonical v1 tracker on the registry side (also folding in #79, which was superseded by this issue).
- SEP-2127: MCP Server Cards —
Feels like a nice-to-have, but it would make sense to allow for ServerCapabilities to be included in
server.jsondata that can get surfaced back to API consumers.