Git Summary vs Core

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

Git Summary logoGit SummaryVersion Control · Local subprocess (stdio)Git repo intelligence: summaries, blame, changelogs, branch health, and history search55GoodAuth: not declaredCore logoCoreVersion Control · Local subprocess (stdio)Personalized GitHub issue finder with multi-strategy search, deep vetting, and viability scoring — CLI, library, MCP server, and Claude Code plugin53GoodAuth: not declared

Verdict: choose Git Summary for version control work as a local process; choose Core 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 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

Core logoChoose Core when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GITHUB_TOKEN.
Explore Core

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGit Summary logoGit SummaryCore logoCore
CategoryVersion ControlVersion Control
Quality signal55/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedGITHUB_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars02
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools6Not listed

Tools & capabilities

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.

Core tools

No tool names declared yet. Check the project README from the listing page.

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 Summary

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

Core

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "oss-scout-core": {
      "command": "npx",
      "args": [
        "-y",
        "@oss-scout/core"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

Git Summary is categorized under Version Control and uses a local stdio subprocess. Core belongs to Version Control and uses a local stdio subprocess. Pick Git Summary for version control work and Core 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 Summary has no declared pricing — check the project's own site. Core 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-summary and oss-scout-core as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Git Summary has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Core has 53/100 (Good) with 1 views, 0 installs and 2 GitHub stars.