Git vs Git Summary

A side-by-side look at the Git and Git Summary MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Git logoGitVersion Control · Local subprocess (stdio)Tools to read, search, and manipulate Git repositories.81ExcellentAuth: no auth requiredGit Summary logoGit SummaryVersion Control · Local subprocess (stdio)Git repo intelligence: summaries, blame, changelogs, branch health, and history search55GoodAuth: not declared

Verdict: choose Git for version control work as a local process; choose Git Summary for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Git logoChoose Git when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like repo_path, context_lines, target.
Explore Git

Git Summary logoChoose Git Summary when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like git_summary, git_changes, git_blame.
Explore Git Summary

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGit logoGitGit Summary logoGit Summary
CategoryVersion ControlVersion Control
Quality signal81/100 · Excellent55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars91,4870
Directory activity 49 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools166

Tools & capabilities

Git tools 16

  • repo_path
  • context_lines
  • target
  • message
  • MERGE_HEAD
  • HEAD
  • files
  • max_count
  • start_timestamp
  • end_timestamp
  • branch_name
  • base_branch
  • +4 more on the listing page

Git Summary tools 6

  • git_summaryGet a structured overview of a Git repository: current branch, recent commits, contributors, and repo stats. Works on any local Git repo.
  • git_changesGet a summary of changes in a commit range: what files changed, who changed them, and a diff stat. Useful for understanding what happened between two points in history.
  • git_blameAnalyze who wrote each line of a file, when, and in which commit. Get top contributors and ownership breakdown. Optionally limit to a line range.
  • git_changelogAuto-generate a changelog from Git commits. Groups commits by type (feat, fix, docs, etc.) using conventional commit format. Specify a range or get the full log.
  • git_branch_healthAnalyze all local branches: find stale branches, merged branches ready for cleanup, and branches that are ahead/behind. Helps keep your repo tidy.
  • git_searchSearch through Git history for commits matching a query. Searches both commit messages and code changes (pickaxe search). Find when a change was introduced or a bug was created.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Git

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git": {
      "command": "uvx",
      "args": [
        "installations"
      ]
    }
  }
}

Git Summary

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "git-summary": {
      "command": "npx",
      "args": [
        "-y",
        "git-summary-mcp"
      ]
    }
  }
}

Frequently asked questions

Git is categorized under Version Control and uses a local stdio subprocess. Git Summary belongs to Version Control and uses a local stdio subprocess. Pick Git for version control work and Git Summary for version control.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Git is listed as free. Auth: no auth required. Git Summary has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add git and git-summary as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 49 views, 0 installs and 91,487 GitHub stars. Git Summary has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.