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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_commit_messageA | Prepare a structured analysis and instruction block for generating a Conventional Commit message from staged git changes only. Behavior: - Validates the repository path and operates on the provided repo or CWD. - Collects staged diff, porcelain status, and a name-status summary. - Incorporates optional user preferences for commit_type and scope. - Returns a single formatted string that includes context plus strict output instructions for an LLM to produce a Conventional Commit. Args: repo_path: Optional path to the target git repository. If not provided, uses the current working directory. commit_type: Optional commit type (feat, fix, docs, style, refactor, perf, build, ci, test, chore, revert) scope: Optional scope of the change Returns: A formatted prompt containing git change context and clear output rules for generating a Conventional Commit message |
| check_git_statusA | Check the current git repository status. Args: repo_path: Optional path to the target git repository. If not provided, uses the current working directory. Returns: Current git status including staged, unstaged, and untracked files |
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 checks git status, the other generates a commit message prompt. There is no overlap in functionality, making them easy to distinguish.
Both tool names follow a consistent verb_noun pattern using snake_case (check_git_status, generate_commit_message), which is predictable and clear.
With only two tools, the server feels thin. While it covers checking status and generating commit messages, the narrow scope makes it borderline acceptable for its stated purpose.
The generate_commit_message tool bundles diff collection and prompt construction, but a separate tool to inspect staged changes directly could be useful. Still, the core workflow is covered without dead ends.