MCP Git Commit Generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | Host to bind the server (default: 0.0.0.0). | 0.0.0.0 |
| port | No | Port to bind the server (default: 3001). | 3001 |
| verbose | No | Verbosity level (e.g., -v, -vv). | |
| transport | No | Transport type (e.g., stdio (default), sse). | stdio |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_commit_messageB | Prepare a prompt for a Conventional Commit message from staged changes only. |
| check_git_statusC | Return staged, unstaged, and untracked files for a Git worktree. |
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 2 tools
The two tools have clearly distinct purposes: one generates a commit-message prompt, while the other inspects Git worktree status. There is no meaningful overlap that would cause an agent to confuse them.
Both names use snake_case with a consistent verb_noun structure. The pattern is predictable and easy to parse.
The server has only 2 tools, which is thin even for a focused utility. They are relevant, but the set feels borderline minimal rather than well-scoped.
For a commit-message generator, the surface covers the core need: checking Git state and preparing a commit prompt from staged changes. Minor gaps remain, such as no direct way to inspect staged diffs separately or execute the commit, but those are outside the stated generator scope.