MCP Git Server
Related Servers
Alternatives to MCP Git Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables LLMs to interact with Git repositories, providing tools to read, search, and manipulate Git repositories through commands like status, diff, commit, and branch management.12MIT
- AlicenseBqualityAmaintenanceA Model Context Protocol server for Git repository interaction and automation. This server provides tools to read, search, and manipulate Git repositories via Large Language Models.1239,753 PyPI90,629MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides Git version control operations as structured tools for AI coding agents. It enables LLMs to programmatically manage repositories through actions like committing changes, rolling back code, and comparing diffs.10Apache 2.0
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables Large Language Models to interact with Git repositories through a robust API, supporting operations like repository initialization, cloning, file staging, committing, and branch management.283,590 npm241Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform standard Git operations like staging, committing, and pushing changes. It facilitates a high-quality, standardized workflow for managing code repositories through natural language commands.148 npm-
- AlicenseCqualityDmaintenanceA Model Context Protocol server that provides 29 Git operations and advanced workflows, enabling AI assistants and developers to safely manage version control.30379 npm1ISC
TDQS
Scored across 22 tools
The tools are mostly distinct, but there is significant overlap in the diff tools (git_diff, git_diff_branches, git_diff_staged, git_diff_unstaged) which could cause confusion, and the GitHub PR tools (github_get_pr_checks, github_get_pr_status) have unclear boundaries. However, descriptions help clarify some differences.
Most tools follow a consistent verb_noun pattern with prefixes (git_ or github_), but there are minor deviations like 'git_create_branch' (verb_noun_noun) and 'github_get_failing_jobs' (verb_adjective_noun) that break the pattern slightly. Overall, the naming is readable and predictable.
With 22 tools, this is borderline heavy for a Git server, as it combines core Git operations with GitHub-specific features, making it feel somewhat overloaded. The count is reasonable but could be streamlined for better focus.
The toolset covers core Git workflows (init, add, commit, push, pull, branch, diff, log) and GitHub PR/CI features well, with no major gaps. Minor gaps include missing tools for merging or rebasing, but agents can work around this using existing commands.