# github [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/davidweb3-ctrl/mcp-github-server  
**GitHub Stars:** 0  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/github-2

## Description
GitHub MCP Server - List PRs, issues, repo info, and search code

## Tools
Capabilities this server exposes over MCP:

- **owner**
- **repo**
- **state**
- **open**
- **closed**
- **all**
- **head**
- **base**
- **sort**
- **direction**
- **per_page**
- **page**
- **pull_number**
- **include_diff**
- **labels**
- **assignee**
- **creator**
- **issue_number**
- **include_comments**
- **query**
- **indexed**
- **best-match**
- **order**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "github": {
    "command": "npx",
    "args": ["-y","@bountyclaw/mcp-github-server"],
    "env": {
      "GITHUB_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `GITHUB_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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`:

```bash
npm install -g @bountyclaw/mcp-github-server
```

Set a GitHub token before starting the process:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/github-2/readme_