MCP Git Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPOSITORY_PATH | No | Path to Git repository |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_statusC | Shows the working tree status |
| git_diff_unstagedB | Shows changes in the working directory that are not yet staged |
| git_diff_stagedC | Shows changes that are staged for commit |
| git_diffC | Shows differences between branches or commits |
| git_commitC | Records changes to the repository |
| git_addC | Adds file contents to the staging area |
| git_resetC | Unstages all staged changes |
| git_logC | Shows the commit logs |
| git_create_branchC | Creates a new branch from an optional base branch |
| git_checkoutC | Switches branches |
| git_showC | Shows the contents of a commit |
| git_initC | Initialize a new Git repository |
| git_pushC | Push commits to remote repository |
| git_pullC | Pull changes from remote repository |
| git_diff_branchesC | Show differences between two branches |
| github_get_pr_checksC | Get check runs for a pull request |
| github_get_failing_jobsC | Get detailed information about failing jobs in a PR |
| github_get_workflow_runC | Get detailed workflow run information |
| github_get_pr_detailsC | Get comprehensive PR details |
| github_list_pull_requestsC | List pull requests for a repository with filtering and pagination |
| github_get_pr_statusC | Get the status and check runs for a pull request |
| github_get_pr_filesC | Get files changed in a pull request with pagination support |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| commit-message | Generate a conventional commit message based on staged changes |
| pr-description | Generate a comprehensive pull request description |
| release-notes | Generate release notes from commit history |
| code-review | Generate a code review prompt for a diff |
| merge-conflict-resolution | Help resolve merge conflicts systematically |
| git-workflow-guide | Guide for Git workflow best practices |
| branch-strategy | Recommend branching strategy for a project |
| git-troubleshooting | Help troubleshoot common Git issues |
| changelog-generation | Generate changelog from commit history |
| rebase-interactive | Guide for interactive rebase operations |
| github-actions-failure-analysis | Analyze GitHub Actions failures and suggest fixes |
| ci-failure-root-cause | Identify root cause of CI failures and provide solutions |
| pr-readiness-assessment | Assess PR readiness and suggest improvements |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.