Log inSubmit server
Github MCP Server logo

Github MCP Server

by github

Connects AI tools to GitHub for repository, code-file, issue, pull request, and workflow tasks over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget

Install Github MCP Server

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://api.githubcopilot.com/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 10/27/2026, 2:48:07 PM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://api.githubcopilot.com/mcp

Overview

github/github-mcp-server connects MCP-compatible AI tools to GitHub, providing repository and code context plus capabilities for issues, pull requests, workflows, and related development tasks. It can run as GitHub-hosted remote MCP over HTTP or as a local server when the host cannot use remote servers. The listed MCP tools include get_file_contents and getFileContents, while remote configuration supports toolsets and OAuth or GitHub PAT authentication. Reach for it when an agent needs GitHub data or repository operations as part of natural-language or multi-step development workflows.

Use cases

  • Read files from a GitHub repository
  • Review issues and pull requests
  • Inspect workflow runs and build failures
  • Analyze repository structure and code
  • Connect an AI host to GitHub context

Key features

  • GitHub repository and code-file access
  • Issue and pull request workflows
  • GitHub Actions and release information
  • Remote HTTP and local deployment options
  • OAuth and personal access token authentication
  • Configurable remote toolsets

Tools2

What Github MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~8 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

21/21 checks healthy over the last 73d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars33kStargazers on the source repository.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Tools exposed2Callable tools this server registers over MCP.
Directory activity9 viewsConfig copies, upvotes, and views on AllMCPs.

How Github MCP Server works

What github/github-mcp-server does

github/github-mcp-server connects AI assistants and agent hosts to GitHub’s platform through the Model Context Protocol. Its documented scope covers repository browsing, code-file access, issue and pull request management, commit and project-structure analysis, GitHub Actions workflow monitoring, release-related work, security findings, Dependabot alerts, discussions, notifications, and team activity.

The tools listed for this server are get_file_contents and getFileContents. These provide access to repository file contents through MCP. The broader GitHub integration is organized around toolsets, which can be selected when configuring the remote server.

How it works

GitHub hosts a remote instance at https://api.githubcopilot.com/mcp/. MCP clients that support remote servers connect to that HTTP endpoint, then authenticate through OAuth or a GitHub personal access token. Hosts using OAuth need a GitHub App or OAuth App configured for remote access; PAT authentication is supported by remote MCP hosts that accept the corresponding authorization header.

A local version is available for MCP hosts that cannot connect to remote servers. The repository also supports an insiders mode for the hosted service, using either an /insiders URL path or the X-MCP-Insiders: true header.

GitHub Enterprise Cloud with data residency can use a corresponding enterprise-specific remote endpoint. GitHub Enterprise Server requires the local server rather than remote server hosting.

Setup and configuration

For VS Code, the remote server requires version 1.101 or newer for remote MCP and OAuth support. Users can install it through the provided VS Code installation flow or add an HTTP server entry manually. The remote configuration can use OAuth, or can send a PAT in an Authorization: Bearer header. A compatible MCP host and any applicable GitHub policies are prerequisites.

The server documentation supports installation guidance for Claude Desktop, Claude Code, Cursor, Windsurf, Codex, Zed, JetBrains-based Copilot environments, and other listed hosts. Remote configuration also accepts toolset settings and advanced headers. Hosts differ in how they configure OAuth and remote MCP connections, so the host-specific installation method matters.

Tools and capabilities

  • Read contents from GitHub repository files with get_file_contents.
  • Read repository file contents through the alternate getFileContents tool name.
  • Browse and query repositories and search project files through the documented GitHub integration scope.
  • Work with issues and pull requests, including triage and review workflows.
  • Inspect Actions runs, build failures, releases, security findings, and Dependabot alerts.
  • Access collaboration-oriented GitHub data such as discussions, notifications, and team activity.

Limitations and notes

Remote access depends on MCP host support and host-specific OAuth configuration. GitHub Enterprise Server is not supported as a remote server host. The insiders endpoint is intended for early access to experimental or newly available tools. Consumers importing the Go module should use the github.com/github/github-mcp-server/v2 module path; the repository notes that the older v2.0.0 tag predates the corrected module path.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Github MCP Server

github/github-mcp-server is an MCP server that connects AI tools to GitHub’s platform for repository and code-file access, issue and pull request work, workflow inspection, and related development tasks. Its listed MCP tools are get_file_contents and getFileContents, and it supports hosted remote or local deployment.

Install the hosted HTTP server through a compatible MCP host, or use the local version when the host lacks remote-server support. VS Code users need version 1.101 or later and can use the provided installation flow or add the GitHub endpoint manually.

Yes, Cursor is listed as a compatible MCP host for the remote GitHub server. Configure Cursor according to its host-specific installation method, then authenticate through OAuth or a GitHub personal access token as supported by the host.

Yes, GitHub Enterprise Cloud with data residency can use an enterprise-specific remote endpoint. GitHub Enterprise Server requires the local server because it does not support remote server hosting.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGithub MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/github-github-mcp-server?style=directory)](https://allmcps.com/mcp/github-github-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/github-github-mcp-server"><img src="https://allmcps.com/api/badge/github-github-mcp-server?style=directory" alt="Github MCP Server on AllMCPs" /></a>