MCP Registry

MCP

MCPDirectoryLevel: Intermediate

MCP Registry

3.5/52dm rating

The official directory for finding servers; still new.

The official directory for finding and publishing MCP servers.

Official site How to use it

Overview

The MCP Registry is the official directory of MCP servers, developed publicly by the community. The repository describes it as something like an app store for MCP servers, where AI applications and users find servers to connect to.

The Registry stores only metadata (descriptive information), not the software packages themselves. The package must first be published on npm, PyPI, NuGet, OCI or MCPB, then the author uses the mcp-publisher tool to submit a server.json file to the Registry. Remote servers can also be registered by URL.

According to the repository, the Registry launched in preview on 08/09/2025 and data may still change or be deleted; the v0.1 API is feature-frozen, and a general availability (GA) release is being planned.

Highlights

Official directory

The site has a search box, a list of recently updated servers and an option to show only the latest versions.

Metadata only

The Registry does not hold source code or install packages, only points to packages published elsewhere.

Name ownership verification

Names of the form io.github.username require GitHub login; custom domains need verification via DNS or HTTP.

Supports many package types

npm, PyPI, NuGet, OCI and MCPB, plus remote servers via Streamable HTTP.

Public API

An API Reference page is available for applications that want to read the server list automatically.

Still in preview

Major changes may occur before it reaches general availability.

What it's for

Finding servers for tools you use

IT teams check whether the business software they use already has an official MCP server.

Publishing the company's server

A software company publishes its MCP server so customers can find and connect to it easily.

Checking a server's origin

See whether the server links to a code repository and a verified domain before installing.

Building an internal catalogue

An internal app reads the Registry API to suggest suitable servers to staff.

How to use it

1
Look up servers
Go to the Registry page, type a keyword and turn on showing only the latest versions.
2
Install the publishing tool
If you want to publish your own server, install mcp-publisher (on macOS, with Homebrew).
$brew install mcp-publisher
3
Create the server.json file
Run it in the server project folder to generate the metadata template, then fill in the description, repository and package.
$mcp-publisher init
4
Sign in to GitHub
Authenticate via GitHub device login to prove your right to the name io.github.your-name.
$mcp-publisher login github
5
Publish
Once the package is on npm or PyPI and mcpName is declared, push the metadata to the Registry.
$mcp-publisher publish

Video guides

MCP Registry Briefing: Standardizing MCP Servers & What It Means for Developers
Agentic AI Foundation

[Session] MCP Registry: The Path To (De-)Centralizing Discovery
Agentic AI Foundation

GitHub MCP Registry integrated in VS Code Insiders
Visual Studio Code

Real-world example

Illustrative scenario

An accounting software startup in Can Tho wrote an MCP server that lets AI assistants look up ledgers. They publish the package to npm, add the mcpName field to package.json, then use mcp-publisher to submit the server to the Registry. Customers using AI apps can find the server by name and check the repository link before connecting.

Tips & notes

Publish the package first
The Registry stores only metadata, so the package must be on npm, PyPI and so on before running publish.
Validate before publishing
Use mcp-publisher's validate command to check server.json without publishing.
Keep the description short
The description field in server.json is limited to 100 characters.
Do not rely on it absolutely during preview
The Registry may still change or reset data, so keep your own records.