Git vs Github MCP
A side-by-side look at the Git and Github MCP 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 Github 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 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 Github MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GITHUB_MCP_ENABLE_WRITE, GITHUB_TOKEN. - You want tools like
get_repo, list_issues, get_issue.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 81/100 · Excellent | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | GITHUB_MCP_ENABLE_WRITEGITHUB_TOKEN |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,526 | 0 |
| Directory activity | 51 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 16 | 14 |
| Full listing | View Git | View Github MCP |
Tools & capabilities
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
Github MCP tools 14
get_repoRepo metadata (stars, language, license, default branch, archived flag...)list_issuesList issues on a repo (PRs filtered out)get_issueFetch a single issuelist_pull_requestsList pull requests on a repoget_pull_requestFetch a single pull requestget_file_contentRead a repo file's content (base64-decoded, binary detected not decoded)search_reposSearch public repositoriesget_userPublic user/org profilelist_commitsList commits on a branch/refcreate_issueOpen an issuecomment_on_issueComment on an issue/PRupdate_issue_stateOpen/close an issue- +2 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.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Github MCP
{
"mcpServers": {
"github-mcp": {
"command": "uvx",
"args": [
"jaimenbell-github-mcp"
],
"env": {
"GITHUB_MCP_ENABLE_WRITE": "YOUR_GITHUB_MCP_ENABLE_WRITE_HERE",
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Git is categorized under Version Control and uses a local stdio subprocess. Github MCP belongs to Version Control and uses a local stdio subprocess. Pick Git for version control work and Github MCP 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 is listed as free. Auth: no auth required. Github MCP 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 github-mcp 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 51 views, 0 installs and 91,526 GitHub stars. Github MCP has 51/100 (Good) with 5 views, 0 installs and 0 GitHub stars.