Bourdon vs Git
A side-by-side look at the Bourdon 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 Bourdon for version control work; choose Git 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 prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Bourdon | |
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 37/100 · Fair | 81/100 · Excellent |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | — | 91,540 |
| Directory activity | 0 views 0 installs 0 upvotes | 51 views 0 installs 0 upvotes |
| Tools | Not listed | 16 |
| Full listing | View Bourdon | View Git |
Tools & capabilities
Bourdon tools
No tool names declared yet. Check the project README from the listing page.
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on 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.
Bourdon
No confirmed install command for Bourdon yet — follow the setup steps linked from its listing page rather than a guessed package name.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}