MCP Git Enhanced
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_diffB | Analyze code changes between commits, branches, or working directory. Provides detailed diff analysis with statistics and file categorization. |
| git_logC | Analyze commit history with filtering and statistics. Provides insights into commit patterns, contributors, and code evolution. |
| git_branchB | Manage and analyze git branches. Provides branch listing, comparison, and management suggestions. |
| git_statusC | Get comprehensive repository status including staged, unstaged, and untracked files. |
| git_commit_analyzeB | Analyze a specific commit in detail including changed files, statistics, and impact. |
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 5 tools
Each tool targets a distinct aspect of git: branches, commits, diffs, log history, and repository status. No functional overlap exists.
All tools follow 'git_' prefix with descriptive nouns, but 'git_commit_analyze' deviates slightly from the single-noun pattern of the others.
Five tools cover essential analysis operations without being excessive or insufficient for the server's stated analytical focus.
Tools provide broad analysis coverage but lack creation or modification operations (e.g., no commit creation, branch creation beyond suggestions), leaving notable gaps for full git workflows.