Git MCP Server
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 |
|---|---|
| initB | Initialize a new Git repository |
| cloneC | Clone a repository |
| statusC | Get repository status |
| addC | Stage files |
| commitC | Create a commit |
| pushC | Push commits to remote |
| pullC | Pull changes from remote |
| branch_listC | List all branches |
| branch_createC | Create a new branch |
| branch_deleteC | Delete a branch |
| checkoutC | Switch branches or restore working tree files |
| tag_listC | List tags |
| tag_createC | Create a tag |
| tag_deleteC | Delete a tag |
| remote_listC | List remotes |
| remote_addC | Add a remote |
| remote_removeC | Remove a remote |
| stash_listC | List stashes |
| stash_saveC | Save changes to stash |
| stash_popC | Apply and remove a stash |
| bulk_actionA | Execute multiple Git operations in sequence. This is the preferred way to execute multiple operations. |
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 21 tools
Every tool has a clearly distinct purpose targeting specific Git operations with no ambiguity. For example, branch_create, branch_delete, and branch_list are clearly differentiated, and tools like stash_save, stash_pop, and stash_list cover distinct aspects of stash management without overlap.
Tool names follow a highly consistent verb_noun pattern throughout, such as branch_create, tag_delete, remote_add, and stash_list. All tools use snake_case with clear, descriptive names that align with Git terminology, making the set predictable and readable.
With 21 tools, the count is borderline high for a Git server, as it includes many specific operations that might be overwhelming. While comprehensive, a typical Git scope could be covered with fewer tools (e.g., 10-15), making this feel slightly heavy but still within reason for the domain.
The tool set provides complete coverage of core Git workflows, including repository management (init, clone), branching (create, delete, list), committing (add, commit), remote operations (add, list, remove, push, pull), and stash/tag handling. No obvious gaps exist, and agents can perform full CRUD/lifecycle operations seamlessly.