Git MCP Server
Related Servers
Alternatives to Git MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceUnified MCP server for Git forge management across GitHub, GitLab, Gitea, and Bitbucket, enabling repository, issue, PR, and CI/CD operations via CLI tools and APIs.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Git repository operations and GitHub PR workflows, allowing users to manage repositories, create branches, commit changes, and create pull requests through natural language.2-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps the GitHub CLI to provide comprehensive access to repository management, pull requests, issues, and workflows. It enables users to perform complex GitHub operations and interact with the GitHub API through a standardized interface.14 npm1ISC
- AlicenseCqualityDmaintenanceAn MCP server that enables communication with GitLab repositories, allowing interaction with GitLab's API to manage projects, issues, and repositories through natural language.45149,894 npm1MIT
- AlicenseBqualityCmaintenanceA comprehensive MCP server that exposes 73 GitHub API tools for managing repositories, pull requests, issues, actions, releases, search, and more, enabling natural language control of GitHub.73MIT
- AlicenseAqualityAmaintenanceA MCP server that bridges LLMs with GitHub repository management, enabling automated analysis of pull requests, issue management, tag creation, and release management through natural language.536Apache 2.0
TDQS
Scored across 23 tools
Most tools have distinct purposes targeting specific resources and actions, but some potential overlap exists between get_file_contents and get_repository_tree for file/directory listing, and between create_comment and list_comments for comment-related operations. Descriptions help clarify boundaries, but an agent might occasionally need to choose between similar tools.
All tool names follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform throughout the set, using snake_case consistently and predictable verb choices like create, get, list, update, merge, push, and search.
With 23 tools, the count is on the higher side for a Git server, bordering on heavy. While the tools cover a broad range of Git and CI/CD operations, some might be considered specialized or redundant, making the surface feel slightly bloated compared to a more minimal set.
The tool set provides comprehensive coverage for Git operations, including repository management, branching, issues, pull requests, CI/CD pipelines, and file operations. It supports full CRUD/lifecycle workflows for key resources like issues and pull requests, with no obvious gaps that would hinder agent functionality.