Github MCP Server vs Git MCP
A side-by-side look at the Github MCP Server and Git MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Github MCP Server for version control work; choose Git MCP 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 Github MCP Server when
- You need dedicated capabilities in the Version Control domain.
Choose Git MCP 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 33/100 · Emerging | 49/100 · Fair |
| 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 | Community listing |
| GitHub stars | 5 | 8,477 |
| Directory activity | 1 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Github MCP Server | View Git MCP |
Tools & capabilities
Github MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Git MCP 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.
Github MCP Server
No confirmed install command for Github MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Git MCP
{
"mcpServers": {
"idosal-git-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote"
]
}
}
}