Git Repo Browser MCP
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 |
|---|---|
| git_directory_structureC | Clone a Git repository and return its directory structure in a tree format. |
| git_read_filesC | Read the contents of specified files in a given git repository. |
| git_branch_diffC | Compare two branches and show files changed between them. |
| git_checkout_branchC | Create and/or checkout a branch. |
| git_delete_branchC | Delete a branch from the repository. |
| git_merge_branchC | Merge a source branch into the current or target branch. |
| git_commit_historyB | Get commit history for a branch with optional filtering. |
| git_commits_detailsC | Get detailed information about commits including full messages and diffs. |
| git_commitC | Create a commit with the specified message. |
| git_trackC | Track (stage) specific files or all files. |
| git_local_changesC | Get uncommitted changes in the working directory. |
| git_search_codeC | Search for patterns in repository code. |
| git_pushC | Push changes to a remote repository. |
| git_pullC | Pull changes from a remote repository. |
| git_stashC | Create or apply a stash. |
| git_create_tagC | Create a tag. |
| git_rebaseC | Rebase the current branch onto another branch or commit. |
| git_configC | Configure git settings for the repository. |
| git_resetC | Reset repository to specified commit or state. |
| git_archiveC | Create a git archive (zip or tar). |
| git_attributesC | Manage git attributes for files. |
| git_blameC | Get blame information for a file. |
| git_cleanC | Perform git clean operations. |
| git_hooksC | Manage git hooks in the repository. |
| git_lfsC | Manage Git LFS (Large File Storage). |
| git_lfs_fetchC | Fetch LFS objects from the remote repository. |
| git_revertC | Revert the current branch to a commit or state. |
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 27 tools
Most tools have distinct purposes targeting specific Git operations, but some overlap exists. For example, git_commit_history and git_commits_details both handle commit information retrieval, and git_clean and git_reset both involve repository state management, which could cause minor confusion. However, descriptions clarify their specific focuses, keeping ambiguity manageable.
All tool names follow a consistent snake_case pattern with a 'git_' prefix and descriptive verb_noun combinations. Examples include git_checkout_branch, git_merge_branch, and git_search_code. This uniformity makes the tool set predictable and easy to navigate for an agent.
With 27 tools, the count is excessive for a Git repository browser. Many tools cover niche or low-level operations that could be consolidated, such as git_lfs and git_lfs_fetch, or git_attributes and git_hooks. This bloated set may overwhelm agents and complicate task selection.
The tool set provides comprehensive coverage of Git operations, including cloning, branching, committing, merging, searching, and configuration. It supports full CRUD and lifecycle management for repositories, with no obvious gaps. Agents can perform end-to-end workflows without dead ends.