git MCP server
OfficialServer 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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_statusB | Shows the working tree status |
| git_diff_unstagedA | Shows changes in the working directory that are 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_addB | Adds file contents to the staging area |
| git_resetA | 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_branchA | List Git branches |
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 12 tools
Each tool targets a distinct Git operation: staging, committing, branching, diffing, logging, etc. The three diff variants are clearly separated by scope (general, staged, unstaged). No two tools have overlapping purposes.
All tools follow the 'git_<action>' pattern with lowercase snake_case. Verbs are clear and consistent (add, branch, checkout, commit, create_branch, diff, etc.), with no mixing of conventions.
12 tools cover the core local Git workflow without being excessive. The number is well-scoped for a focused Git assistant, allowing agents to perform common tasks without overwhelming options.
The set covers staging, committing, branching, and diffing, but lacks essential operations like merge, rebase, remote actions (push/pull/fetch), branch deletion, and repository initialization. These gaps limit the workflow to basic local operations.