Side-by-side comparison

Both tools were last committed on March 13, 2026 — equally fresh. The key difference is deployment model: the official server runs locally and uses the GitHub API; git-mcp is a remote server you connect to by URL with no local install required.

Data from March 19, 2026 crawl. modelcontextprotocol/servers star count reflects the full monorepo, not only server-github. Mode = how the MCP server is deployed and accessed.

Official GitHub MCP server

github/github-mcp-server — score 85.44

github/github-mcp-server is maintained directly by GitHub and scores 85.44 in the AgentRank index — the second-highest in the API integration category after Google Workspace MCP. It has 27,865 stars and 111 contributors.

The official server wraps the GitHub REST and GraphQL APIs into MCP tools. Agents can: list and create repositories, open and close issues, create pull requests, review PRs, run code searches, trigger GitHub Actions workflows, and read repository contents. It requires a GitHub personal access token and runs as a local Go binary.

The Go implementation (rather than TypeScript) reflects GitHub's choice to ship a fast, dependency-light binary. The official backing means it tracks GitHub API changes — when GitHub adds a new API surface, the MCP server typically follows within weeks.

git-mcp

idosal/git-mcp — score 75.44

idosal/git-mcp takes a different architectural approach: it is a remote MCP server. Instead of running a local binary, you add a URL to your MCP config and the server runs in the cloud. No installation required. 7,759 stars and 16 contributors.

The use case is narrower but the friction is dramatically lower. Point git-mcp at any public GitHub or GitLab repository, and agents can read the repository's code, README, documentation, and file tree — without setting up a token or running a local process. The primary purpose is eliminating code hallucinations: agents that can read the actual library source produce more accurate code.

git-mcp does not support write operations (creating issues, opening PRs, etc.) — it is a read-only tool optimized for documentation and source code ingestion. The AgentRank score (75.44) reflects solid freshness (March 13 commit) and good adoption, but lower contributor depth than the official server.

Verdict

The AgentRank score difference (85.44 vs 75.44) is real but not the whole picture. These tools solve different problems:

• Need to write to GitHub (issues, PRs, workflows, private repos): github/github-mcp-server — score 85.44, official, 111 contributors, full API surface.
• Need to read any public repo without setup: idosal/git-mcp — score 75.44, remote server, no token required, zero installation.
• Running both simultaneously is valid: Use git-mcp for reading external public repos and the official server for your own GitHub organization's write operations. MCP clients support multiple servers.

For the widest coverage, the combination is: official GitHub server (authenticated, write-capable) + git-mcp (anonymous read, zero setup) configured simultaneously. Your agent uses each based on the task.

Setup guide

Install Official GitHub MCP server

{
  "mcpServers": {
    "github": {
      "command": "github-mcp-server",
      "args": ["stdio"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..."
      }
    }
  }
}

Install the binary: brew install github/gh/gh-mcp or download from the GitHub releases page.

Add git-mcp (remote, no install)

{
  "mcpServers": {
    "git-mcp": {
      "url": "https://gitmcp.io/docs"
    }
  }
}

Replace the URL with any public GitHub repo: https://gitmcp.io/{owner}/{repo}. No token required. For Claude Desktop, add as an MCP server with type sse.