MCP Registry launched: Public MCP servers at a glance
The registry, which has been released as a preview, is intended to help find publicly available MCP servers. Developers can add their servers.
(Image: tomertu/Shutterstock.com)
The development team behind the Model Context Protocol (MCP) has introduced the MCP Registry as a preview – an open catalog and API to discover and use publicly available MCP servers. MCP is an open protocol for large language models (LLMs) to access external data sources.
Add and find public MCP servers
A few months ago, the MCP team announced on GitHub that they were working on a central registry for the MCP ecosystem. The open-source MCP registry that has now been published is intended to standardize the process of how MCP servers are distributed and discovered. It allows server maintainers to add their servers and client maintainers to access server data.
To add a server to the registry, it must be published on a package registry such as npm, PyPI, or DockerHub. Detailed instructions can be found on GitHub. There, developers can find out how to create a server.json file for their server, achieve authentication with the registry, publish their server, and verify the publication.
Dealing with sub-registries
As the MCP team emphasizes, the central registry should serve as the main source of truth for publicly available MCP servers but should not get in the way of existing community and company registries. These can create public or private sub-registries in the MCP registry, as the MCP team describes on GitHub.
Existing collections include a long, well-maintained list on GitHub and a Docker directory for MCP sources.
Videos by heise
As the MCP registry is currently a preview, there is no guarantee that the data it contains will be consistent. Breaking changes are also possible before the registry reaches general availability.
Further information can be found on the MCP blog.
(mai)
