Git Prompts 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 |
|---|---|
| git-diffB | Get a diff between the HEAD and the ancestor branch or commit |
| git-cached-diffA | Get a diff between the files in the staging area (the index) and the HEAD |
| git-commit-messagesB | Get commit messages between the ancestor and HEAD |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate-pr-desc | Generate PR Description based on the diff between the HEAD and the ancestor branch or commit |
| generate-commit-message | Generate commit message based on the diff between the files in the staging area (the index) and the HEAD |
| git-diff | Generate a diff between the HEAD and the ancestor branch or commit |
| git-cached-diff | Generate a diff between the files in the staging area (the index) and the HEAD |
| git-commit-messages | Get commit messages between the ancestor and HEAD |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have overlapping purposes focused on git diffs and commit history, which could cause confusion. git-cached-diff and git-diff both produce diffs but target different git states, while git-commit-messages retrieves commit messages. The descriptions help clarify the distinctions, but the domain overlap is significant.
All tool names follow a consistent 'git-' prefix with hyphenated descriptive terms (cached-diff, commit-messages, diff). This pattern is predictable and readable throughout the set, with no deviations in style or convention.
With only 3 tools, the server feels thin for a git-related domain, which typically involves more operations like status, log, branch, or push. While the tools cover specific diff and commit message scenarios, the scope appears limited and potentially incomplete for general git workflows.
For a git server, there are significant gaps in the tool surface. It lacks basic operations such as viewing status, checking out branches, pushing/pulling changes, or creating commits. The tools only cover diff and commit message retrieval, leaving most git workflows unsupported and likely to cause agent failures.