ai-commit-helper-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_commit_contextB | Get the staged Git diff and effective commit-message rules for a local repository. Returns a status of "changes" or "no_changes", the diff, and the rules to use when generating commit-message suggestions. |
| validate_commit_messageA | Validate a proposed commit message against the target repository's configured format and maximum subject length. Returns whether the message is valid and a list of validation errors. |
| create_commit_rulesB | Create a .commit-helper.json file in the repository root using the user's chosen commit-message rules. Fails if the file already exists. |
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 3 tools
Each tool has a clearly distinct role: one retrieves context (diff + rules), one validates a message, one writes a rules file. There is no realistic overlap that would cause an agent to pick the wrong tool.
All three tools follow a strict verb_noun snake_case pattern (get_/validate_/create_ + commit-related noun). The naming is predictable and self-documenting.
Three tools is on the thin side but fits a narrowly scoped commit-message helper; each tool earns its place. No filler or redundant tools are present.
The read/validate/create surface is coherent, but create_commit_rules explicitly fails when a config already exists and there is no update or delete counterpart, leaving a real dead end for modifying rules. Agents would have to fall back to manual file editing for edits or removal.