Git 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 |
|---|---|
| get_last_git_tagA | Find the last git tag in the repository |
| list_commits_since_last_tagB | List commit messages since main HEAD and the last git tag |
| list_repositoriesB | List all git repositories in the configured path |
| create_git_tagB | Create a new git tag in the repository |
| push_git_tagB | Push a git tag to the default remote |
| refresh_repositoryB | Refresh repository by checking out main branch and pulling all remotes |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: creating tags, getting the last tag, listing commits since the last tag, listing repositories, pushing tags, and refreshing repositories. The descriptions reinforce these distinct functions, making misselection unlikely.
The naming follows a consistent verb_noun pattern (e.g., create_git_tag, list_commits_since_last_tag) with clear, descriptive names. The only minor deviation is 'refresh_repository' which uses 'refresh' instead of a more common verb like 'update', but it still fits the pattern and is understandable.
With 6 tools, this server is well-scoped for managing git repositories, focusing on tag operations and repository maintenance. Each tool serves a specific, useful function without bloat, making the count appropriate for the domain.
The toolset covers tag management and basic repository operations well, but there are notable gaps in the git domain, such as creating commits, branching, merging, or handling remotes beyond pushing tags. This limits agents from performing full git workflows, though the provided tools are coherent for their specific scope.