Log inSubmit server
Github MCP Server logo

Github MCP Server

GitHub automation MCP server with 112 internal tools, code-first execution, compact responses, and workflow, repository, and security coverage.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Github MCP Server

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

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for github-mcp-server, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

The github-mcp-server MCP server connects AI clients to GitHub through a code-first interface that exposes an execute_code tool and provides access to 112 internal GitHub tools. It supports repository and file management, issues, pull requests, Actions, security features, projects, discussions, notifications, users, teams, gists, labels, and stars. Compact, JSON, and Markdown response formats help control context size, with compact responses reducing the size of many results by 80–97%. Reach for it when an agent needs to inspect or modify GitHub resources, monitor development workflows, or perform multi-step GitHub operations while limiting response tokens.

Use cases

  • Search repositories and code
  • Review and update pull requests
  • Manage issues, comments, and labels
  • Monitor GitHub Actions runs
  • Inspect repository security findings

Key features

  • 112 internal GitHub tools
  • Code-first execute_code interface
  • Compact, JSON, and Markdown responses
  • GitHub Actions workflow management
  • Repository security operations
  • Issue, pull request, and file management

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.

Adoption & maintenance

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

GitHub stars5Stargazers on the source repository.
Last commit2mo agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Github MCP Server works

What github-mcp-server does

The github-mcp-server MCP server gives AI clients access to GitHub workflow operations through a Python-based MCP implementation. Its coverage includes repositories, branches, files, issues, pull requests, comments, releases, gists, labels, users, organizations, collaborators, teams, projects, discussions, notifications, and repository stars.

It also includes GitHub Actions operations for workflows, runs, jobs, and artifacts. Security-related capabilities cover Dependabot, code scanning, secret scanning, and security advisories. Some operations require appropriate GitHub permissions, especially those involving repository administration or security data.

The project is designed for agents that need to perform both read and write operations. Examples include finding code, reviewing pull requests, creating or updating files, adding issue comments, managing labels, triggering workflows, and handling selected repository resources.

How it works

The current architecture exposes one MCP-facing tool, execute_code. An agent writes TypeScript code that calls the available GitHub operations on demand rather than receiving the schemas for every operation in its initial context. This code-first design is intended to reduce initialization and prompt token usage.

The implementation contains 112 internal tools, while the MCP client sees the execution entry point. Tool discovery functions can list available tools, search for tools by keyword, and return a tool's schema and examples. This lets an agent identify an operation without loading every definition up front.

The github-mcp-server MCP server supports three response formats. compact is intended for lists, discovery, and status checks; json returns full structured data; and markdown produces human-readable output. Compact output is available on 26 tools and is reported as 80–97% smaller for supported operations. Pull request overviews can use GraphQL to reduce the response size compared with the REST equivalent.

Tools and capabilities

  • Manage repositories, branches, files, releases, and gists.
  • Search code and users, inspect repository data, and retrieve authenticated-user context.
  • List, create, update, and comment on issues and pull requests.
  • Monitor and operate GitHub Actions workflows, runs, jobs, and artifacts.
  • Work with Dependabot, code scanning, secret scanning, and security advisories.
  • Manage classic project boards, columns, discussions, notifications, labels, collaborators, and teams.
  • Star and unstar repositories and list their stargazers.
  • Use compact, JSON, or Markdown output where supported.

Limitations and notes

The MCP-facing surface is a single execute_code tool, so clients and agents must use the project's code-first calling model rather than expecting 112 separately exposed tools. The internal tool count and supported operations may differ from the number visible in an MCP client's tool list.

GitHub access still depends on the authentication method and permissions available to the server. The project documents personal access token and GitHub App authentication, with GitHub App installations providing higher stated rate limits and fine-grained permissions. Security and repository-management operations may require additional access.

The repository targets Python 3.10 or newer. The README identifies the project as AGPL version 3 and reports version 2.5.7 in its badges.

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-mcp-server is an MCP server that connects AI clients to GitHub. Its exposed execute_code tool provides on-demand access to 112 internal tools for repositories, files, issues, pull requests, Actions, security features, projects, discussions, notifications, users, teams, gists, labels, and stars.

It reduces token usage through a code-first interface and compact response formats. Clients receive the execute_code entry point, while agents discover and call internal tools on demand. Supported compact responses are reported as 80–97% smaller than full responses, depending on the operation.

Yes, github-mcp-server supports GitHub Actions operations. Its internal tools cover workflows, workflow runs, jobs, and artifacts, allowing an agent to inspect and manage those resources through the code-first execute_code interface.

The required permissions depend on the security operation and GitHub authentication setup. The project documents permission requirements for Dependabot, code scanning, and secret scanning tools, so the token or GitHub App installation must have access to the requested repository data.

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-mcp-server-2?style=directory)](https://allmcps.com/mcp/github-mcp-server-2)
HTML Embed
<a href="https://allmcps.com/mcp/github-mcp-server-2"><img src="https://allmcps.com/api/badge/github-mcp-server-2?style=directory" alt="Github MCP Server on AllMCPs" /></a>