registry/docs/server-registry-api
Repository files (latest commit first)
Filename Latest commit message Latest commit date
adam jones d3cde5d3aa
fix: remove id property from Server schema (#339)
The Server schema should not have its own `id` property as the ID is
managed by the registry system through the
`_meta["io.modelcontextprotocol.registry"].id` field.

Fixes #336

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
Co-authored-by: adam jones <domdomegg@users.noreply.github.com>
2025-09-02 14:51:06 +01:00
..
openapi.yaml fix: remove id property from Server schema (#339) 2025-09-02 14:51:06 +01:00
README.md api: Use Huma to generate swagger docs and parse JSON automatically (#262) 2025-08-13 16:57:55 +01:00

Registry API

There are a variety of use cases where an MCP Server Registry API is useful to the MCP ecosystem. At least the following:

  • Implementation of a centralized, publicly available catalog of all publicly accessible MCP server implementations
  • Implementation of a private catalog of MCP server implementations exclusively accessible by a specific group of people (e.g. a single enterprise)

These scenarios would benefit from a standard "MCP server registry API" specification that they could potentially compose, as well as share resources (like SDK implementations).

The centralized, publicly available catalog ("Official MCP Registry") needs additional constraints that need not apply to the broader "MCP server registry API"

References:

  • openapi.yaml - A reusable API specification (MCP Server Registry API) that anyone building any sort of "MCP server registry" should consider adopting / aligning with.
  • https://registry.modelcontextprotocol.io/openapi.yaml - The specification backing the Official MCP Registry; a derivative of the MCP Server Registry API specification.