Published on

It's happening: An official MCP server registry

Table of Contents

Goal

A single source of truth "centralized metaregistry" for MCP servers. Server maintainers can push their metadata to the registry. Other registries can can consume that metadata, filter it, curate it, and serve it to MCP Clients and other end users.

Summary

The registry won't serve end users of MCPs, it will be a central registry to serve other registry/search platforms go for ground truth info

  • e.g. your Claude instance won't go to this registry to query for an MCP server. Claude will use a registry that was built from data maintained in this "centralized metaregistry"

They will define a json format to be used for describing an MCP server. This will help make the MCP protocol easier to integrate an adopt. The format will include a minimal set of info

  • references to source code/packages/container locations
  • descriptive metadata (e.g. name, description)
  • installation command (e.g. npx ..., uvx ...)
  • versioning of the data stored in the registry

Out of scope

Massive scale & reliability (millions of consumers): The maximum number of direct consumers of this metaregistry is roughly equal to "number of MCP client apps", rather than "number of MCP client app users".

Solving the long tail of MCP filtering & curation capabilities: MCP Client IDE's will need a different way to sort/filter compared to MCP Client chat apps, compared to MCP Client agent-building frameworks. The registry may allow for optional data that helps here, but don't plan on them storing it for you.

Reusability of infrastructure, implementation detail decisions: The goal is to define the what information is kept in the registry and how it's formatted, but not to specify how to run a registry (e.g. infrastructure and implementation details).

Security assurances: Initially there's no plan to use the registry to improve security for MCP servers (although maybe in the future)

References