MCP Registry vs Package Registry
People think the MCP Registry is like npm for MCP servers. It is not. A package registry such as npm or PyPI stores the code you download. The MCP Registry stores no code at all. It holds a short listing for each server, with its name and where to get it, and that points back to npm, PyPI, Docker Hub or a web address.
Package Registry
A website that keeps packages so anyone can get them by name.
A package registry is a website that stores packages so anyone can download them. Each language has its main one. JavaScript has the npm registry. Python has the Python Package Index, called PyPI. Your package manager asks it for a name and a version, then gets it. Companies also run their own, kept private.
MCP Registry
The official public list of MCP servers. It says where to get each one.
The MCP Registry is the official public list of MCP servers. Each entry is a server.json file with the server's name, what it does and where to get it. It holds only this data, not the code, which stays on npm, PyPI or Docker Hub. Names are tied to a GitHub account or a web domain, so no one can pose as you. It is still in preview.
In one line
- Package Registry
- A website that keeps packages so anyone can get them by name.
- MCP Registry
- The official public list of MCP servers. It says where to get each one.
These live in different corners of the glossary (Development and AI), which is exactly why they get confused.