What happened
Report Provider: GitHub Blog
Author: Toby Padilla, Principal Product Manager at GitHub, leading MCP initiatives.
Date: Published on September 16, 2025.
This is your new home base for discovering MCP servers. Learn how we’re working with the broader community on MCP publication and discovery. Share: If you’ve tried connecting AI agents to your development tools, you know the pain: MCP servers scattered across numerous registries, random repos, buried in community threads — making discovery slow and full of friction without a central place to go.
Meanwhile, MCP server creators are worn out from publishing to multiple places and answering the same setup questions again and again. The result is a fractured environment that’s fraught with potential security risks. Today, we’re taking the first step toward solving this challenge. The GitHub MCP Registry launches as your new home base for discovering MCP servers.
Whether you’re building with GitHub Copilot, agents, or any AI tool that speaks MCP, this is the place to find what you need. With GitHub already home to most MCP servers, the MCP Registry makes them dramatically easier to discover, explore, and use — helping developers find the right tools faster and contribute to a more open, interoperable ecosystem.
Browse the MCP Registry today and start building with the tools that power agentic workflows. Inside the GitHub MCP Registry We’re starting simple and building in the open. The MCP Registry launches with a curated directory of MCP servers from leading partners and the open source community. Each server is backed by its GitHub repository, so you can learn what it does, how to get started, and make informed choices quickly.
Here’s what you’ll find: Discoverability inside VS Code with one-click installation Signal over noise with servers sorted by GitHub stars and community activity Works with your stack including GitHub Copilot and any MCP-compatible host From day one, the MCP Registry is shaped by contributions from across the ecosystem — including our launch partners who are helping define what the quality of MCP servers look like.
This collaborative foundation ensures developers have access to tools they can trust, and sets the stage for a healthier, more interoperable AI ecosystem. With the launch of GitHub’s MCP Registry, developers can easily bring Figma context into Copilot through our Dev Mode MCP server, accelerating their design-to-code workflow by generating code that’s both production-ready and aligned with their design system.
Anna Kohnen, VP of Business Development, Figma At Postman, we see MCP as a foundational layer of the AI agents stack and a vital part of building AI-ready APIs. The GitHub MCP Registry helps developers access the entire Postman platform from inside their coding assistants, further bridging the gap between code, documentation, and execution in a way that wasn’t possible before.
Bajali Raghavan, Head of Engineering, Postman Terraform empowers developers with consistent infrastructure management. With the launch of GitHub’s MCP Registry, they can now easily discover official MCP servers, such as HashiCorp’s Terraform MCP server, and add them to their workflows with a single click—making it faster than ever to bring Terraform’s capabilities into day-to-day development.
Chris Audie, SVP Product Management, HashiCorp (an IBM Company) By bringing the Dynatrace MCP server to the GitHub MCP Registry, developers get AI-powered observability, security, and performance insights right at their fingertips—so teams can deliver faster, more resilient, and more robust software with less context switching and reduced cognitive load.
We’ve seen rapid adoption across our own engineering organization because the integrated agentic AI experience helps our developers to ship faster and with more confidence—all without leaving their IDEs. Bonifaz Kaufmann, VP Product, Dynatrace We’re also excited to include the Remote GitHub MCP Server, which recently launched in general availability.
It allows agents to connect with the rich context found in GitHub repositories, issues, and pull requests — unlocking deeper, multi-step agentic workflows. Its inclusion in the registry reinforces our commitment to open interoperability and gives developers a trusted way to integrate GitHub context into any MCP-compatible tool.
Building an open ecosystem together The launch of the GitHub MCP Registry is just the beginning. We’re working closely with Anthropic and the MCP Steering Committee to build an open-source MCP registry that integrates seamlessly with GitHub’s. Together with the broader community, we’re shaping the open standard and contribution model for MCP.
Developers will be able to self-publish MCP servers directly to the OSS MCP Community Registry. Once published, those servers will automatically appear in the GitHub MCP Registry, creating a unified, scalable path for discovery. This publication flow will: Reduce duplication across registries Surface transparent metadata and verification signals Enable contribution at scale across the ecosystem The result is a healthier, more open ecosystem — one that leads with quality and accelerates innovation.
The road ahead Together with the open source community, Anthropic, and the MCP Steering Committee, we’re building an open ecosystem where discovering the right AI capability is as simple as searching GitHub. The GitHub MCP Registry is your fastest path from idea to integration, and the foundation for a healthier, more interoperable AI toolchain.
Ready to explore? Browse the GitHub MCP Registry to discover curated MCP servers from across the ecosystem. You can also contribute to the OSS MCP Community Registry and help shape the future of open agentic workflows. Let’s build the future of AI tooling together! Written by Toby Padilla is a Principal Product Manager and leads GitHub’s MCP initiatives.
Related posts We do newsletters, tooDiscover tips, technical guides, and best practices in our biweekly newsletter just for devs.
Source coverage
Report Provider: GitHub Blog
Author: Toby Padilla, Principal Product Manager at GitHub, leading MCP initiatives.
Deeper analysis
Full source content
This is your new home base for discovering MCP servers. Learn how we’re working with the broader community on MCP publication and discovery. Share: If you’ve tried connecting AI agents to your development tools, you know the pain: MCP servers scattered across numerous registries, random repos, buried in community threads — making discovery slow and full of friction without a central place to go.
Meanwhile, MCP server creators are worn out from publishing to multiple places and answering the same setup questions again and again. The result is a fractured environment that’s fraught with potential security risks. Today, we’re taking the first step toward solving this challenge. The GitHub MCP Registry launches as your new home base for discovering MCP servers.
Whether you’re building with GitHub Copilot, agents, or any AI tool that speaks MCP, this is the place to find what you need. With GitHub already home to most MCP servers, the MCP Registry makes them dramatically easier to discover, explore, and use — helping developers find the right tools faster and contribute to a more open, interoperable ecosystem.
Browse the MCP Registry today and start building with the tools that power agentic workflows. Inside the GitHub MCP Registry We’re starting simple and building in the open. The MCP Registry launches with a curated directory of MCP servers from leading partners and the open source community. Each server is backed by its GitHub repository, so you can learn what it does, how to get started, and make informed choices quickly.
Here’s what you’ll find: Discoverability inside VS Code with one-click installation Signal over noise with servers sorted by GitHub stars and community activity Works with your stack including GitHub Copilot and any MCP-compatible host From day one, the MCP Registry is shaped by contributions from across the ecosystem — including our launch partners who are helping define what the quality of MCP servers look like.
This collaborative foundation ensures developers have access to tools they can trust, and sets the stage for a healthier, more interoperable AI ecosystem. With the launch of GitHub’s MCP Registry, developers can easily bring Figma context into Copilot through our Dev Mode MCP server, accelerating their design-to-code workflow by generating code that’s both production-ready and aligned with their design system.
Anna Kohnen, VP of Business Development, Figma At Postman, we see MCP as a foundational layer of the AI agents stack and a vital part of building AI-ready APIs. The GitHub MCP Registry helps developers access the entire Postman platform from inside their coding assistants, further bridging the gap between code, documentation, and execution in a way that wasn’t possible before.
Bajali Raghavan, Head of Engineering, Postman Terraform empowers developers with consistent infrastructure management. With the launch of GitHub’s MCP Registry, they can now easily discover official MCP servers, such as HashiCorp’s Terraform MCP server, and add them to their workflows with a single click—making it faster than ever to bring Terraform’s capabilities into day-to-day development.
Chris Audie, SVP Product Management, HashiCorp (an IBM Company) By bringing the Dynatrace MCP server to the GitHub MCP Registry, developers get AI-powered observability, security, and performance insights right at their fingertips—so teams can deliver faster, more resilient, and more robust software with less context switching and reduced cognitive load.
We’ve seen rapid adoption across our own engineering organization because the integrated agentic AI experience helps our developers to ship faster and with more confidence—all without leaving their IDEs. Bonifaz Kaufmann, VP Product, Dynatrace We’re also excited to include the Remote GitHub MCP Server, which recently launched in general availability.
It allows agents to connect with the rich context found in GitHub repositories, issues, and pull requests — unlocking deeper, multi-step agentic workflows. Its inclusion in the registry reinforces our commitment to open interoperability and gives developers a trusted way to integrate GitHub context into any MCP-compatible tool.
Building an open ecosystem together The launch of the GitHub MCP Registry is just the beginning. We’re working closely with Anthropic and the MCP Steering Committee to build an open-source MCP registry that integrates seamlessly with GitHub’s. Together with the broader community, we’re shaping the open standard and contribution model for MCP.
Developers will be able to self-publish MCP servers directly to the OSS MCP Community Registry. Once published, those servers will automatically appear in the GitHub MCP Registry, creating a unified, scalable path for discovery. This publication flow will: Reduce duplication across registries Surface transparent metadata and verification signals Enable contribution at scale across the ecosystem The result is a healthier, more open ecosystem — one that leads with quality and accelerates innovation.
The road ahead Together with the open source community, Anthropic, and the MCP Steering Committee, we’re building an open ecosystem where discovering the right AI capability is as simple as searching GitHub. The GitHub MCP Registry is your fastest path from idea to integration, and the foundation for a healthier, more interoperable AI toolchain.
Ready to explore? Browse the GitHub MCP Registry to discover curated MCP servers from across the ecosystem. You can also contribute to the OSS MCP Community Registry and help shape the future of open agentic workflows. Let’s build the future of AI tooling together! Written by Toby Padilla is a Principal Product Manager and leads GitHub’s MCP initiatives.
Related posts We do newsletters, tooDiscover tips, technical guides, and best practices in our biweekly newsletter just for devs.
How this page is built
Goose Pod turns cited reporting into a public episode summary first, then pairs that summary with audio playback so listeners can check the source material before they decide how deeply to engage.
The goal is to make this page useful as a news landing page first, while still giving listeners transcript access, related episodes, and direct links back to the original publishers.
