How to Access the Official MCP Registry API and Documentation

Updated

The Official MCP Registry exposes its API through three base URLs — Production (registry.modelcontextprotocol.io), Staging (staging.registry.modelcontextprotocol.io), and Local (localhost:8080) — and links to its documentation and API reference directly from the registry landing page. Use Production for real integrations, Staging for testing against pre-release data, and Local when running the registry on your own machine.

Where the Entry Points Live

The registry homepage surfaces three navigation links:

  • GitHub — source code and project activity
  • Docs — written documentation
  • API Reference — the endpoint-level specification for calling the API

The page also notes the registry is "Built in the open by MCP contributors," so the GitHub link is the place to check for changes, issues, or contribution guidance.

Choosing an API Base URL

The registry lets you switch between environments from a server selector on the page. The three options and their intended use:

Environment Base URL When to use it
Production registry.modelcontextprotocol.io Live integrations and anything you ship
Staging staging.registry.modelcontextprotocol.io Testing against non-production data before promoting
Local localhost:8080 Running the registry locally for development

Select the environment, then confirm with Apply; Cancel dismisses the change. The current selection is shown next to "Server:" on the page.

How to Get Started

  1. Open the registry site and pick the environment you want to target (Production, Staging, or Local).
  2. Click API Reference to see the available endpoints and their request/response formats.
  3. Point your client at the matching base URL — for example, registry.modelcontextprotocol.io for production calls.
  4. If you need background on the data model or usage guidance, follow the Docs link; for source-level detail, use GitHub.

Common Pitfalls

  • Mixing environments. A base URL from Staging will not return production data. Confirm the "Server:" label before debugging unexpected results.
  • Assuming Local works out of the box. localhost:8080 only responds if you are running the registry locally; it is not a hosted endpoint.
  • Skipping the API Reference. The base URL tells you where to send requests, not how — endpoint paths, parameters, and response shapes come from the API Reference.

What You Can Browse Alongside the API

The registry homepage also lists servers under Recently Updated, with a Show only latest versions filter and a search box. This is useful for discovering what is currently published before you write code against the API.