Server facts
mcp-git-commit-generator
Project
- Author
- theoklitosBam7
- License
- Not specified
- Category
- Version Control
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 9
- Last commit
- Data as of
Tags
- commit generator
- git
- mcp
Overview
Staged Git changes provide the starting point for mcp-git-commit-generator’s commit-drafting workflow. Developers can first call check_git_status to inspect which files are staged, modified but unstaged, or untracked. The generate_commit_message tool then validates the repository location and gathers the staged diff alongside status information and a file-change summary. Its result is a formatted prompt containing repository context and output rules for an LLM, rather than a completed commit operation. Optional commit_type and scope inputs let users supply preferences for the Conventional Commit message. Both tools accept a repository path and otherwise work from the current directory.
The documented workflow keeps staging and committing separate: users stage their edits, request a message through their MCP client, and then commit with that message. Setup options include uvx, a PyPI installation, and a published Docker image. Client configuration examples cover VS Code, Cursor, Windsurf, and Claude Desktop. The README also describes default stdio communication, an SSE option, and interactive inspection through MCP Inspector.
mcp-git-commit-generator setup notes
- mcp-git-commit-generator records stdio only; confirm a network transport upstream before planning remote access.
- mcp-git-commit-generator has no recorded license; confirm reuse terms in its repository.