
Git Commit Generator
Analyzes your staged git changes and automatically generates properly formatted conventional commit messages. Works by examining diffs and file status to suggest appropriate commit types and scopes.
Generates conventional commit messages from staged git changes by analyzing diffs and file status to create properly formatted commits with optional type and scope parameters.
What it does
- Generate conventional commit messages from staged changes
- Analyze git diffs and file modifications
- Check current git repository status
- Auto-detect commit type and scope
- Format commits following conventional standards
Best for
About Git Commit Generator
Git Commit Generator is a community-built MCP server published by theoklitosbam7 that provides AI assistants with tools and capabilities via the Model Context Protocol. Generate conventional commit messages from staged git changes. Streamline your git amend commit message process with aut It is categorized under productivity, developer tools. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.
How to install
You can install Git Commit Generator in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
Git Commit Generator is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Tools (2)
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 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
MCP Git Commit Generator
Generate conventional commit messages from your staged git changes using Model Context Protocol (MCP).
β¨ Features
- π€ Automatic commit message generation based on staged git diffs
- π Conventional Commits support with auto-detection of type and scope
- π Multiple transport options - stdio (default) and SSE for different use cases
- π Inspector UI for interactive testing and debugging
- π³ Docker support with pre-built images for easy deployment
- β‘ Cross-platform - works on macOS, Linux, and Windows
π¦ Requirements
- For Docker usage: Docker (for running the server in a container)
- For PyPI/uvx usage: Python >= 3.13.5 and uv (recommended) or pip
- Git (for version control)
- An MCP-compatible client (VS Code with MCP extension, Claude Desktop, Cursor, Windsurf, etc.)
π Installation
You can install and use the MCP Git Commit Generator in multiple ways:
Option 1: Using uvx (Recommended)
The easiest way to use the package is with uvx, which automatically manages the virtual environment:
uvx mcp-git-commit-generator
Option 2: Install from PyPI
pip install mcp-git-commit-generator
Or with uv:
uv pip install mcp-git-commit-generator
Option 3: Using Docker
Use the pre-built Docker image from GitHub Container Registry (no installation required):
docker run -i --rm --mount type=bind,src=${HOME},dst=${HOME} ghcr.io/theoklitosbam7/mcp-git-commit-generator:latest
π οΈ Available Tools
This MCP server provides the following tools to help you generate conventional commit messages:
generate_commit_message
Generates a conventional commit message based on your staged git changes.
Parameters:
repo_path(string, optional): Path to the git repository. If omitted, uses the current directory.commit_type(string, optional): Conventional commit type (e.g.,feat,fix,docs,style,refactor,perf,build,ci,test,chore,revert). If omitted, the type will be auto-detected.scope(string, optional): Scope of the change (e.g., file or module name). If omitted, the scope will be auto-detected based on changed files.
Usage:
- Stage your changes:
git add <files> - Use the tool through your MCP client to generate a commit message
- The tool will analyze your staged changes and generate an appropriate conventional commit message
check_git_status
Checks the current git repository status, including staged, unstaged, and untracked files.
Parameters:
repo_path(string, optional): Path to the git repository. If omitted, uses the current directory.
Usage:
Use this tool to get an overview of your current git repository state before generating commit messages.
π§© MCP Client Configuration
Configure the MCP Git Commit Generator in your favorite MCP client. You have multiple options:
- Using uvx (recommended - automatically manages dependencies)
- Using Docker (no local Python installation required)
- Using local Python installation (for development)
VS Code
Add one of the following configurations to your VS Code mcp.json file (usually located at .vscode/mcp.json in your workspace):
Using uvx (Recommended)
{
"servers": {
"mcp-git-commit-generator": {
"command": "uvx",
"args": ["mcp-git-commit-generator"]
}
}
}
Using Docker
{
"servers": {
"mcp-git-commit-generator": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount",
"type=bind,src=${userHome},dst=${userHome}",
"ghcr.io/theoklitosbam7/mcp-git-commit-generator:latest"
]
}
}
}
If you want to put the configuration in your user settings.json file, you can do so by adding:
{
"mcp": {
"servers": {
"mcp-git-commit-generator": {
"command": "uvx",
"args": ["mcp-git-commit-generator"]
}
}
}
}
Cursor
Add one of the following to your Cursor MCP configuration file (usually located at ~/.cursor/mcp.json):
Cursor with uvx (Recommended)
{
"mcpServers": {
"mcp-git-commit-generator": {
"command": "uvx",
"args": ["mcp-git-commit-generator"]
}
}
}
Cursor with Docker
{
"mcpServers": {
"mcp-git-commit-generator": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount",
"type=bind,src=${userHome},dst=${userHome}",
"ghcr.io/theoklitosbam7/mcp-git-commit-generator:latest"
]
}
}
}
Windsurf
Configure Windsurf with one of the following MCP server settings (usually located at ~/.codeium/windsurf/mcp_config.json):
Windsurf with uvx (Recommended)
{
"mcpServers": {
"mcp-git-commit-generator": {
"command": "uvx",
"args": ["mcp-git-commit-generator"]
}
}
}
Windsurf with Docker
{
"mcpServers": {
"mcp-git-commit-generator": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount",
"type=bind,src=${userHome},dst=${userHome}",
"ghcr.io/theoklitosbam7/mcp-git-commit-generator:latest"
]
}
}
}
Claude Desktop
Add one of the following to your Claude Desktop configuration file (usually located at
~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
Claude Desktop with uvx (Recommended)
{
"mcpServers": {
"mcp-git-commit-generator": {
"command": "uvx",
"args": ["mcp-git-commit-generator"]
}
}
}
Claude Desktop with Docker
{
"mcpServers": {
"mcp-git-commit-generator": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--mount",
"type=bind,src=${userHome},dst=${userHome}",
"ghcr.io/theoklitosbam7/mcp-git-commit-generator:latest"
]
}
}
}
Note: The
--mountoption in Docker configurations allows the Docker container to access your home directory, enabling it to work with git repositories located anywhere in your file system. When using uvx or pip installations, this mounting is not needed as the tool runs directly on your system. Adjust the mount path if your repositories are located elsewhere when using Docker.
π Quick Start Guide
-
Install the package using one of the methods above:
- Recommended:
uvx mcp-git-commit-generator(or configure in your MCP client) - Alternative:
pip install mcp-git-commit-generator - Docker: Use the configurations above with Docker
- Recommended:
-
Configure your MCP client using one of the configurations above
-
Stage some changes in a git repository:
git add <files> -
Use the tools through your MCP client:
- Use
check_git_statusto see your current repository state - Use
generate_commit_messageto create a conventional commit message
- Use
-
Commit your changes with the generated message
π¨βπ» Developer Guidelines
The following sections are intended for developers who want to contribute to or modify the MCP Git Commit Generator.
Local Development Setup π οΈ
If you prefer not to use Docker for development, you can run the server locally:
Requirements:
- Python >= 3.13.5
- uv (recommended for dependency management and local development)
- Node.js (for Inspector UI, optional)
- Python Debugger Extension (for debugging, optional)
Note: The MCP CLI dependency is automatically installed via
uv.lockwhen usinguv sync.
Installation:
-
Clone the repository:
git clone https://github.com/theoklitosBam7/mcp-git-commit-generator.git cd mcp-git-commit-generator -
Prepare environment:
There are two approaches to set up the environment for this project. You can choose either one based on your preference.
Note: Reload VSCode or terminal to ensure the virtual environment python is used after creating the virtual environment.
Approach Steps Using uv(Recommended)1. Create virtual environment and install dependencies: uv sync --group dev
2. Run VSCode Command "Python: Select Interpreter" and select the python from.venvdirectory
3. The project is installed in editable mode automatically byuv sync.Using pip1. Create virtual environment: python -m venv .venv
2. Run VSCode Command "Python: Select Interpreter" and select the python from created virtual environment
3. Install dependen
README truncated. View full README on GitHub.
Alternatives
Related Skills
Browse all skillsAutomatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Automated meeting preparation and daily commit summaries. Use when checking Google Calendar for upcoming meetings, generating standup updates from GitHub commits, or sending daily development summaries. Pulls meeting schedules and commit history, then formats verbose developer-friendly updates.
Essential development workflow agents for code review, debugging, testing, documentation, and git operations. Includes 7 specialized agents with strong auto-discovery triggers. Use when: setting up development workflows, code reviews, debugging errors, writing tests, generating documentation, creating commits, or verifying builds.
Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.
UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
Create well-structured git commits in logical chunks following best practices