By package registry
MCP servers by package registry
13,314 of the MCP Registry servers with a page here can be run locally from a package. The registry entry names the package registry, the identifier and usually the version; the package itself lives on that registry, not in the MCP Registry.
Servers per package registry
A server published to more than one registry is counted under each.
| npm | 8,832 | |
|---|---|---|
| PyPI | 3,187 | |
| OCI image (Docker) | 878 | |
| MCP Bundle (.mcpb) | 810 | |
| NuGet | 108 | |
| Cargo (crates.io) | 63 |
How each kind of package runs
npm
A Node.js package published to the npm registry. Needs Node.js; clients usually start it with npx.
PyPI
A Python package published to PyPI. Needs Python; clients usually start it with uvx (from uv) or after pip install.
OCI image (Docker)
A container image in an OCI registry such as Docker Hub or GitHub Container Registry. Needs Docker or another OCI container runtime; started with docker run.
MCP Bundle (.mcpb)
An MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it. Needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
NuGet
A .NET package published to NuGet. Needs the .NET SDK; run as a .NET tool.
Cargo (crates.io)
A Rust crate published to crates.io. Needs the Rust toolchain; cargo install builds the program.