by theoklitosbam7
Generate conventional commit messages from staged git changes. Streamline your git amend commit message process with aut
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.
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.
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.
MIT
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: Git Commit Generator is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Git Commit Generator against two servers with overlapping tools; this profile had the clearer scope statement.
Git Commit Generator is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Strong directory entry: Git Commit Generator surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Git Commit Generator is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Git Commit Generator is the kind of server we cite when onboarding engineers to host + tool permissions.
Strong directory entry: Git Commit Generator surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Git Commit Generator is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Git Commit Generator has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, Git Commit Generator benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 49
Generate conventional commit messages from your staged git changes using Model Context Protocol (MCP).
You can install and use the MCP Git Commit Generator in multiple ways:
The easiest way to use the package is with uvx, which automatically manages the virtual environment:
uvx mcp-git-commit-generator
pip install mcp-git-commit-generator
Or with uv:
uv pip install mcp-git-commit-generator
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
This MCP server provides the following tools to help you generate conventional commit messages:
generate_commit_messageGenerates 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:
git add <files>check_git_statusChecks 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.
Configure the MCP Git Commit Generator in your favorite MCP client. You have multiple options:
Add one of the following configurations to your VS Code mcp.json file (usually located at .vscode/mcp.json in your workspace):
{
"servers": {
"mcp-git-commit-generator": {
"command": "uvx",
"args": ["mcp-git-commit-generator"]
}
}
}
{
"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"]
}
}
}
}
Add one of the following to your Cursor MCP configuration file (usually located at ~/.cursor/mcp.json):
{
"mcpServers": {
"mcp-git-commit-generator": {
"command": "uvx",
"args": ["mcp-git-commit-generator"]
}
}
}
{
"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"
]
}
}
}
Configure Windsurf with one of the following MCP server settings (usually located at ~/.codeium/windsurf/mcp_config.json):
{
"mcpServers": {
"mcp-git-commit-generator": {
"command": "uvx",
"args": ["mcp-git-commit-generator"]
}
}
}
{
"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"
]
}
}
}
Add one of the following to your Claude Desktop configuration file (usually located at
~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"mcp-git-commit-generator": {
"command": "uvx",
"args": ["mcp-git-commit-generator"]
}
}
}
{
"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.
Install the package using one of the methods above:
uvx mcp-git-commit-generator (or configure in your MCP client)pip install mcp-git-commit-generatorConfigure 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:
check_git_status to see your current repository stategenerate_commit_message to create a conventional commit messageCommit your changes with the generated message
The following sections are intended for developers who want to contribute to or modify the MCP Git Commit Generator.
If you prefer not to use Docker for development, you can run the server locally:
Requirements:
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 <br>2. Run VSCode Command "Python: Select Interpreter" and select the python from .venv directory <br>3. The project is installed in editable mode automatically by uv sync. |
Using pip | 1. Create virtual environment: python -m venv .venv <br>2. Run VSCode Command "Python: Select Interpreter" and select the python from created virtual environment <br>3. Install dependen |
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.