Log inSubmit server

Hidden while we check this listing

Our automated checks found a problem, so this listing is out of search, browse and the API until it clears. It comes back on its own once the problem is fixed.

  • Package no longer on the registry
Own this project? Claim it
Github logo

Github

Connects AI assistants to GitHub for pull requests, issues, repository metadata, and code search.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Github

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

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "github-2": {
      "command": "npx",
      "args": [
        "-y",
        "@bountyclaw/mcp-github-server"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

npx -y @bountyclaw/mcp-github-server

npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@bountyclaw%2fmcp-github-server - Not found npm ERR! 404 npm ERR! 404 '@bountyclaw/mcp-github-server@*' is not in this registry. npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url. npm ERR! A complete log of this run can be found in: /home/user/.npm/_logs/2026-10-20T11_20_41_486Z-debug-0.log

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 4d ago.

Overview

The github MCP server gives AI assistants MCP tools for browsing GitHub pull requests and issues, inspecting repository metadata, and searching code. It uses a GitHub token supplied through the GITHUB_TOKEN environment variable and can run through an npx-based MCP configuration. Reach for it when an agent needs read access to repository activity or code without switching to a separate GitHub interface. The available operations cover six tools for listing and viewing pull requests and issues, retrieving repository information, and searching code.

Use cases

  • List open pull requests for a repository
  • Inspect an issue with its comments
  • Review a pull request diff
  • Retrieve repository statistics
  • Search GitHub code with a query

Key features

  • Pull request listing and details
  • Issue listing and details
  • Optional pull request diffs
  • Optional issue comments
  • Repository metadata and statistics
  • GitHub code search

Tools23

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

Self-reported~40 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.

9/9 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12h ago via OSV.dev · @bountyclaw/mcp-github-server (npm)

Adoption & maintenance

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

Last commit6mo agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Tools exposed23Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Github works

What the github MCP server does

The github MCP server exposes GitHub repository information through the Model Context Protocol. It focuses on read-oriented workflows: an assistant can list or inspect pull requests, list or inspect issues, retrieve repository statistics and metadata, and search code using GitHub code-search syntax.

The six documented tools are github_pr_list, github_pr_view, github_issue_list, github_issue_view, github_repo_info, and github_search_code. Repository-scoped operations require an owner and repository name. Pull request and issue detail tools also require the relevant number.

How it works

An MCP client starts the server as a Node package, then sends tool calls with structured inputs. The server uses the configured GitHub token to perform the requested GitHub operation and returns the resulting information to the assistant.

Pull request listing supports state, head branch, base branch, sorting, direction, and pagination filters. A pull request view can optionally include the diff. Issue listing supports state, labels, assignee, creator, sorting, direction, and pagination; issue details can optionally include comments. Code search accepts a query, optional sort and order settings, and pagination controls.

Setup and configuration

Install the package globally with npm, or let an MCP client run it through npx:

Terminal
npm install -g @bountyclaw/mcp-github-server

Set a GitHub token before starting the process:

server.ts
export GITHUB_TOKEN=your_github_token_here

For Claude Code, the documented configuration uses npx -y @bountyclaw/mcp-github-server as the command and passes GITHUB_TOKEN in the server environment.

Tools and capabilities

The github MCP server provides these capabilities:

  • List pull requests with branch, state, sort, and pagination filters.
  • View a pull request and optionally include its diff.
  • List issues using state, label, assignee, creator, sort, and pagination filters.
  • View an issue and optionally include its comments.
  • Retrieve repository information and statistics.
  • Search code across GitHub with GitHub query syntax.

Limitations and notes

A GitHub token is required for the documented setup. Pull request pagination allows a maximum of 100 results per page. Code search expects GitHub code-search syntax, so query behavior follows that syntax rather than a separate server-specific language.

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

github is an MCP server that connects AI assistants to GitHub repositories. Its main tools list and view pull requests, list and view issues, retrieve repository information and statistics, and search code with GitHub query syntax. It authenticates with a GitHub token supplied through the GITHUB_TOKEN environment variable.

Install it with npm using `npm install -g @bountyclaw/mcp-github-server`, or configure an MCP client to run it with `npx -y @bountyclaw/mcp-github-server`. Set `GITHUB_TOKEN` in the process environment before starting the server.

Yes, github works with Claude Code through the documented MCP configuration. Add the server with `npx` as the command, use `-y` and the package name as arguments, and provide `GITHUB_TOKEN` in the server's environment settings.

Yes, the github MCP server includes `github_search_code` for searching code across GitHub. It accepts a required query using GitHub code-search syntax, with optional sort, order, result-count, and page parameters.

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 AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/github-2?style=directory)](https://allmcps.com/mcp/github-2)
HTML Embed
<a href="https://allmcps.com/mcp/github-2"><img src="https://allmcps.com/api/badge/github-2?style=directory" alt="Github on AllMCPs" /></a>