Data as of

GitHub MCP Server for Claude Desktop: Setup & Config

GitHub MCP Server connects Claude Desktop to repository content, issues, pull requests, and platform workflows.

What you can do with GitHub in Claude Desktop

Give agents GitHub-native repository context and issue, review, workflow, and security operations.

  • Explore repositories, files, and commit history through an assistant.
  • Triage issues and manage pull request workflows.
  • Investigate failed GitHub Actions runs and development pipeline activity.

Before you start: GitHub in Claude Desktop

  • Docker installed and running for local container execution
  • An MCP-compatible host
  • GitHub authentication and appropriate account permissions

The command uses the README's local PAT-based Docker example. The remote URL uses HTTP and supports OAuth where the host implements it, or PAT authentication. Grant only the permissions required for your tasks.

GitHub Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For GitHub MCP Server, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add GitHub MCP Server to Claude Desktop

    Use the github-mcp-server entry below in mcpServers. Keep GitHub MCP Server's documented stdio connection fields and your other Claude Desktop entries.

  3. Check GitHub MCP Server in Claude Desktop

    GitHub MCP Server: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "mcpServers": {
    "github-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GITHUB_PERSONAL_ACCESS_TOKEN",
        "ghcr.io/github/github-mcp-server"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<your GitHub personal access token with appropriate permissions>"
      }
    }
  }
}

Troubleshooting GitHub in Claude Desktop

  • Fully quit and reopen Claude Desktop for GitHub MCP Server. If docker and a running Docker engine is missing, check the desktop process's PATH, which may differ from your terminal.
  • In Claude Desktop's GitHub MCP Server entry, check GITHUB_PERSONAL_ACCESS_TOKEN. Keep secrets out of shared screenshots and repositories.
  • GitHub MCP Server uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: OAuth support and configuration vary by MCP host.
  • Known limitation: GitHub Enterprise Server cannot use the hosted remote service.
  • Known limitation: Individual tool names are not stated in the supplied README excerpt.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

GitHub MCP Server — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads GitHub MCP Server from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's github-mcp-server example uses stdio.

GitHub MCP Server's Claude Desktop configuration invokes docker and a running Docker engine.

Claude Desktop's GitHub MCP Server example references GITHUB_PERSONAL_ACCESS_TOKEN. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

No. GitHub also provides a hosted remote endpoint for MCP hosts that support remote connections.

Yes. The README documents local OAuth login and Docker callback-port configuration. A PAT remains an alternative and takes precedence when configured.