Git vs Core
A side-by-side look at the Git and Core MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git for version control work; 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?
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You want tools like
git_log, git_diff, git_blame.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 37/100 · Fair | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | GITHUB_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Git | View Core |
Tools & capabilities
Git tools 5
git_logGet commit history with filtering by author, date range, and file pathgit_diffShow diff between commits, branches, or tags with change summariesgit_blameShow who last modified each line of a file with commit infogit_statsRepository statistics: commits, contributors, activity over time, most changed filesgit_branchList branches with last commit info, ahead/behind counts, merged/unmerged status
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
No confirmed install command for Git yet — follow the setup steps linked from its listing page rather than a guessed package name.
Core
{
"mcpServers": {
"oss-scout-core": {
"command": "npx",
"args": [
"-y",
"@oss-scout/core"
],
"env": {
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Git is categorized under Version Control and uses an install path we have not confirmed yet. Core belongs to Version Control and uses a local stdio subprocess. Pick Git 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 has no confirmed install command yet — follow its own setup instructions.
Git 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-2 and oss-scout-core 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 37/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Core has 53/100 (Good) with 1 views, 0 installs and 2 GitHub stars.