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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusB | Get the current git repository status. |
| addB | Add files to the git staging area. |
| commitB | Commit staged changes to the git repository. |
| logB | View commit history and log information from a git repository. |
| create-branchB | Create a new git branch, optionally from a specific starting point. |
| checkoutB | Switch branches, commits, or restore working tree files. |
| resetB | Reset repository state (soft, mixed, hard). |
| diffB | Show differences between commits, branches, files. |
| showB | Display commit details and changes. |
| initB | Initialize new Git repository. |
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 10 tools
Each tool has a clearly distinct purpose targeting specific Git operations, with no ambiguity or overlap. For example, 'add' handles staging files, 'commit' handles committing staged changes, and 'status' provides repository state, all serving unique functions in the Git workflow.
Tool names are mostly consistent using imperative verbs (e.g., add, checkout, commit) with clear, concise terms, though 'create-branch' uses a hyphen while others do not, and 'log' and 'show' are nouns rather than verbs, causing minor deviations from a strict pattern.
With 10 tools, the set is well-scoped for Git operations, covering essential commands like init, add, commit, and branch management. Each tool earns its place by addressing core Git functionalities without redundancy or excessive complexity.
The toolset provides complete coverage of the Git domain, including repository initialization, staging, committing, branching, diffing, history viewing, and state management. It supports full CRUD-like workflows (e.g., create, read, update, delete via commands like add, log, reset) with no obvious gaps for typical agent tasks.