Git vs GitResume
A side-by-side look at the Git and GitResume MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
GitResumeVersion Control · Remote HTTP/SSEValidate, build, and publish the resume you keep as YAML in your own GitHub repository.39FairAuth: oauth 2.0Verdict: choose Git for version control work as a local process; choose GitResume for version control over a hosted endpoint. 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.
GChoose GitResume when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G GitResume | |
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 81/100 · Excellent | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,540 | — |
| Directory activity | 51 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 16 | Not listed |
| Full listing | View Git | View GitResume |
Tools & capabilities
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
GitResume 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
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
GitResume
{
"mcpServers": {
"gitresume": {
"command": "npx",
"args": [
"-y",
"gitresume"
]
}
}
}
Frequently asked questions
Git is categorized under Version Control and uses a local stdio subprocess. GitResume belongs to Version Control and uses a remote HTTP/SSE transport. Pick Git for version control work and GitResume 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. GitResume has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 gitresume 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,540 GitHub stars. GitResume has 39/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.