One Registry for MCP Servers

MCP servers have been scattered across registries, random repositories and community threads, making discovery slow and full of friction. Creators, meanwhile, have had to publish to multiple places and repeatedly answer the same setup questions. GitHub is stepping in with the MCP Registry, a curated directory that puts MCP servers in a central, searchable location.

The registry is live now at github.com/mcp. Each listed server is backed by its GitHub repository, so developers can review what it does and how to get started before installing. The initial catalog includes servers from launch partners and the open source community, with sorting based on GitHub stars and community activity to surface what's actually being used.

Key features from day one include:

  • Discoverability inside VS Code with one-click installation
  • Servers sorted by GitHub stars and community activity to prioritize signal over noise
  • Compatibility with GitHub Copilot and any MCP-compatible host

The Remote GitHub MCP Server, recently released in general availability, is also included. It lets agents pull context from GitHub repositories, issues, and pull requests for multi-step agentic workflows.

An Open Path for Publishers

The registry launch is a first step in a larger effort. GitHub is working with Anthropic and the MCP Steering Committee to build an open-source MCP registry that integrates with GitHub's. Developers will be able to self-publish MCP servers to the OSS MCP Community Registry, and once published, those servers will automatically appear in the GitHub MCP Registry.

That publication flow is designed to:

  • Reduce duplication across registries
  • Expose transparent metadata and verification signals
  • Enable contribution at scale across the ecosystem

The stated goal is a healthier ecosystem — one where the discovery of AI capabilities is as simple as searching GitHub, and where quality improvements come from community contributions rather than fragmented directories. For developers, the immediate benefit is a faster path from finding an MCP server to integrating it into their toolchain.