ai-commit-helper-mcp
Related Servers
Alternatives to ai-commit-helper-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceAutomatically generates conventional commit messages from staged git changes and checks repository status. Analyzes git diffs to create properly formatted commit messages following conventional commit standards.29MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to read a project's git diff and generate Angular-style, company-standard commit messages, then stage and commit the changes on the user's behalf. It runs on the host's built-in AI capabilities with no API key or cost, exposing tools for fetching changes, staging all files, and committing.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to audit git diffs, scan for leaked secrets and unsafe APIs, detect breaking changes, triage issues, generate changelogs, and assess repository hygiene through native stdio JSON-RPC tools.7Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with tools to run git status, recent commits, tests, and linter on a real repository.ISC
- AlicenseNot gradedqualityBmaintenanceEnables Codex users to review workspace and staged files, preview diffs, stage or unstage changes, generate AI-written Chinese Conventional Commit messages from staged diffs, and switch, merge, update, and push branches from a local panel. All Git operations run through a locally registered MCP service without a cloud deployment.MIT
- FlicenseBqualityCmaintenanceEnables Codex to delegate coding tasks to a locally hosted Qwen model through an MCP tool, which can read, write, patch, test, and inspect git diffs inside an allowed workspace.11-
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.