Git vs Git
A side-by-side look at the Git and Git 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 as a local process; choose Git for version control. 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 prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You want tools like
git_log, git_diff, git_blame.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 81/100 · Excellent | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,487 | 0 |
| Directory activity | 48 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 16 | 5 |
| Full listing | View Git | View Git |
Tools & capabilities
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
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
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": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Git
No confirmed install command for Git yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Git is categorized under Version Control and uses a local stdio subprocess. Git belongs to Version Control and uses an install path we have not confirmed yet. Pick Git for version control work and Git 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 is listed as free. Auth: no auth required. Git 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-2 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 48 views, 0 installs and 91,487 GitHub stars. Git has 37/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.