mcp-git
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_statusB | Shows the working tree status |
| git_diff_unstagedA | Shows changes in working directory not yet staged |
| git_diff_stagedA | Shows changes that are staged for commit |
| git_diffC | Shows differences between branches or commits |
| git_commitC | Records changes to the repository |
| git_addA | 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 |
| git_checkoutC | Switches branches |
| git_showC | Shows the contents of a commit |
| git_initB | Initializes a Git repository |
| git_stashB | Stashes changes in working directory |
| git_stash_popB | Applies and removes a single stashed state |
| git_stash_applyA | Applies a single stashed state without removing it |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Every tool has a clearly distinct purpose and targets a different Git operation. There is no ambiguity between tools like git_diff, git_diff_staged, and git_diff_unstaged, or between git_stash, git_stash_apply, and git_stash_pop.
All tools follow the consistent 'git_<verb>' pattern with snake_case. The naming is uniform and predictable, making it easy for an agent to infer tool behavior from its name.
With 15 tools, the server is well-scoped for a Git client. It covers essential operations without being overwhelming or too sparse. Each tool serves a clear purpose in the standard Git workflow.
The tool set covers core local Git operations such as staging, committing, branching, diffing, stashing, and log viewing. However, it lacks tools for remote operations like push, pull, fetch, and merge, which are important for typical Git usage and might require agents to work around.