34,360
stars
+164+192
5,321
forks
–
watchers
–
prs
–
issues
–
releases
–
discussions
README
GitHub MCP Server
The GitHub MCP Server connects AI tools directly to GitHub's platform. This gives AI agents, assistants, and chatbots the ability to read repositories and code files, manage issues and PRs, analyze code, and automate workflows. All through natural language interactions.
Use Cases
- Repository Management: Browse and query code, search files, analyze commits, and understand project structure across any repository you have access to.
- Issue & PR Automation: Create, update, and manage issues and pull requests. Let AI help triage bugs, review code changes, and maintain project boards.
- CI/CD & Workflow Intelligence: Monitor GitHub Actions workflow runs, analyze build failures, manage releases, and get insights into your development pipeline.
- Code Analysis: Examine security findings, review Dependabot alerts, understand code patterns, and get comprehensive insights into your codebase.
- Team Collaboration: Access discussions, manage notifications, analyze team activity, and streamline processes for your team.
Built for developers who want to connect their AI tools to GitHub context and capabilities, from simple natural language queries to complex multi-step agent workflows.
Using the Go module
The Go module path is github.com/github/github-mcp-server/v2. Library consumers
must use this prefix in imports, for example
github.com/github/github-mcp-server/v2/pkg/github, and in go get commands.
No /v2 subdirectory is needed when building from a repository checkout.
The existing v2.0.0 tag predates this module-path correction and cannot be used
as a Go module. After this change is merged, a new release such as v2.0.1 must
be tagged from a commit containing the corrected module path. Until then,
consumers can use a pseudo-version from a commit containing this change.
---
Remote GitHub MCP Server
The remote GitHub MCP Server is hosted by GitHub and provides the easiest method for getting up and running. If your MCP host does not support remote MCP servers, don't worry! You can use the local version of the GitHub MCP Server instead.
Prerequisites
1. A compatible MCP host with remote server support (VS Code 1.101+, Claude Desktop, Cursor, Windsurf, etc.)
2. Any applicable policies enabled
Install in VS Code
For quick installation, use one of the one-click install buttons above. Once you complete that flow, toggle Agent mode (located by the Copilot Chat text input) and the server will start. Make sure you're using VS Code 1.101 or later for remote MCP and OAuth support.
Alternatively, to manually configure VS Code, choose the appropriate JSON block from the examples below and add it to your host configuration:
Using OAuthUsing a GitHub PAT
VS Code (version 1.101 or greater)
json
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/"
}
}
}
json
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/",
相关报道 (5)
News & coverage (14)
Hacker NewsGitHub's Official MCP Server▲ 6 · 0 comments · 2025-04-07Hacker NewsGitHub MCP Server▲ 5 · 2 comments · 2025-04-04SD TimesNew Relic Change Tracking Brings Headless Intelligent Observability Directly into GitHub Copilot2026-10-29MarketScreenerNew Relic Announces Suite Of Integrations For GitHub Copilot2026-10-28newapi.varindia.comNew Relic Integrates Change Tracking into GitHub Copilot2026-10-28MarketScreenerNew Relic kündigt eine Reihe von Integrationen für GitHub Copilot an2026-10-28MarketScreenerNew Relic anuncia un conjunto de integraciones para GitHub Copilot2026-10-28ZonebourseNew Relic annonce une série d’intégrations pour GitHub Copilot2026-10-28AOLNew Relic Change Tracking Brings Headless Intelligent Observability Directly into GitHub Copilot, Empowering Developers to Ship Code with Confidence2026-10-27The GitHub BlogGitHub MCP Server supports the next MCP specification2026-07-23