MCP Git Commit Generator
Related Servers
Alternatives to MCP Git Commit Generator
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAnalyzes git changes in repositories and generates conventional commit messages using OpenAI's GPT models, supporting both staged and unstaged changes with detailed summaries.16 npm15MIT
- AlicenseAqualityDmaintenanceAnalyzes Git repository changes and generates conventional, context-aware commit messages using the Model Context Protocol.15MIT
- AlicenseNot gradedqualityNot gradedmaintenanceAnalyzes git repository changes to generate conventional commit messages and summaries using OpenAI's GPT-4o-mini. It provides detailed tracking of modified, added, and deleted files to streamline the version control process.16 npm-
- AlicenseAqualityDmaintenanceGenerates commit messages, PR titles and descriptions, and release notes from git changes, with automatic domain detection for appropriate PR templates.104 npm1MIT
- 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
- AlicenseAqualityDmaintenanceEnables AI assistants to create conventional Git commits, update changelogs, and optionally push changes to remote repositories.22MIT
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.