GitHub Plus MCP Server

Model Context Protocol server for GitHub API integration

Local serverstdioTypeScript

What is the GitHub Plus MCP server?

Most developer tooling work still happens through a UI a human drives. GitHub Plus MCP server moves it into the conversation instead. Model Context Protocol server for GitHub API integration.

The short version

MCP Server for the GitHub API, enabling file operations, repository management, search functionality, and more.

  • Automatic Branch Creation — When creating/updating files or pushing changes, branches are automatically created if they don't exist
  • Comprehensive Error Handling — Clear error messages for common issues
  • Git History Preservation — Operations maintain proper Git history without force pushing
  • Batch Operations — Support for both single-file and multi-file operations with content or file paths
  • Advanced Search — Support for searching code, issues/PRs, and users

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • Inputs — - owner (string): Repository owner (username or organization)
  • Returns — File content and commit details
  • Features — The Features tool exposed by this server

What it needs from you

Configuration is passed through the environment: GITHUB_PERSONAL_ACCESS_TOKEN, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. GitHub Plus's toolset — Inputs, Returns, Features — is a fair guide to whether it matches your workflow. It is maintained by PhialsBasement; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against GitHub Plus's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
Inputs- owner (string): Repository owner (username or organization)
ReturnsFile content and commit details
FeaturesThe Features tool exposed by this server.

How to install the GitHub Plus MCP server

{
  "mcpServers": {
    "github": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GITHUB_PERSONAL_ACCESS_TOKEN",
        "mcp/github"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
GITHUB_PERSONAL_ACCESS_TOKENCredential the server authenticates with.Yes
YOUR_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use GitHub Plus to Inputs.
  • Use GitHub Plus to Returns.
  • Use GitHub Plus to Features.

Frequently asked questions

It connects GitHub Plus to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Inputs, Returns, Features) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with GitHub Plus directly.