Skip to main content
Glama
MCP Git Commit Generator

MCP Git Commit Generator

by LuiccianDev

Python 3.13+ Code style: black Imports: isort Type checking: mypy Ruff GitPython pre-commit License: MIT

A Python package implementing the Model Context Protocol (MCP) to generate meaningful Git commit messages by analyzing repository changes.


πŸš€ Overview

MCP Git Commit Generator is a Python package that leverages the Model Context Protocol (MCP) to analyze your Git repository and generate conventional, context-aware commit messages. It supports multiple deployment modes and integrates seamlessly with DXT and MCP environments.


Related MCP server: Git Auto Commit MCP Server

πŸ› οΈ Tool Reference

For a complete list of available tools and their input schemas, see TOOLS.md.


πŸ“¦ Installation

Prerequisites

  • Python 3.11+ (with type hints)

  • UV Package Manager (Install UV) or use pip

  • Git (for repository operations)

  • Desktop Extensions (DXT) (Install DXT) for packaging .dxt files for Claude Desktop

Clone the Repository

git clone https://github.com/LuiccianDev/mcp_git_commit_generator.git
cd mcp_git_commit_generator

Install in Development Mode

pip install -e .

πŸ“‚ Project Structure

mcp_git_commit_generator/
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ core/                  # Core logic and utilities
β”‚   β”‚   └── __init__.py
β”‚   β”œβ”€β”€ tools/                 # MCP tool implementations
β”‚   β”‚   β”œβ”€β”€ __init__.py
β”‚   β”‚   β”œβ”€β”€ commit_analysis.py # Commit message generation logic
β”‚   β”‚   β”œβ”€β”€ git_operations.py  # Git repository operations
β”‚   β”‚   └── register_tools.py  # Tool registration for MCP
β”‚   β”œβ”€β”€ __init__.py            # Package metadata
β”‚   β”œβ”€β”€ __main__.py            # CLI entry point
β”‚   └── server.py              # MCP server implementation
β”œβ”€β”€ tests/                     # Unit and integration tests
β”‚   └── test_commit_analysis.py
β”œβ”€β”€ manifest.json              # DXT packaging manifest
β”œβ”€β”€ TOOLS.md                   # Tool reference documentation
└──README.md                  # Project documentation

πŸ§ͺ Development

Setup Development Environment

  1. Clone the repository and navigate to the project directory.

  2. Install development dependencies:

    pip install -e ".[dev]"
  3. Install pre-commit hooks:

    pre-commit install

βš™οΈ Deployment Modes

MCP Git Commit Generator Server supports three deployment modes to fit different workflows and environments:

DXT Package Deployment

Recommended for: Users in the DXT ecosystem who want seamless configuration management.

  1. Package the project:

    dxt pack
  2. Usage: Once packaged, the tool integrates directly with DXT-compatible clients with automatic user configuration variable substitution.

  3. Server Configuration: This project includes manifest.json for building the .dxt package.

For more details, see DXT Package Documentation.

Traditional MCP Server

Recommended for: Standard MCP server deployments with existing MCP infrastructure.

Add to your MCP configuration file (e.g., Claude Desktop's mcp_config.json):

# Build packages
uv build
# Install packages
pip install dist/your_package*.whl

Then configure MCP:

{
  "mcpServers": {
    "mcp_git_commit": {
      "command": "uv",
      "args": ["run", "mcp_git_commit"]
    }
  }
}

Or use this configuration (less recommended):

{
   "mcp-word": {
      "command": "/Users/user/to/repo/.venv/Scripts/python",
      "args": [
        "/Users/user/to/repo/src/mcp_git_commit_generator/server.py"
      ]
   }
}

🀝 Contributing

Contributions are welcome! Please read the contribution guidelines before submitting pull requests.


πŸ“œ License

This project is licensed under the MIT License - see the LICENSE file for details.


Available Tools

15 tools
generate_commit_messageA

Analyses staged changes and produces a conventional commit message suggestion.

Reads staged diffs and file metadata to generate a commit message in the format type(scope): description. The LLM should use the returned analysis to craft the final message.

Inputs: repo_path (required), commit_type, scope, lite_mode. Returns: result

git_add_toolA

Adds file contents to the staging area.

Inputs: repo_path (required), files (required). Returns: result

git_branch_toolB

Lists Git branches (local, remote, or all).

Inputs: repo_path (required), branch_type, contains, not_contains. Returns: result

git_checkout_toolC

Switches to the specified branch.

Inputs: repo_path (required), branch_name (required). Returns: result

git_commit_toolB

Records staged changes to the repository with the given commit message.

Inputs: repo_path (required), message (required). Returns: result

git_create_branch_toolB

Creates a new branch from an optional base branch.

Inputs: repo_path (required), branch_name (required), base_branch. Returns: result

git_diff_staged_toolB

Shows changes that are staged for commit.

Inputs: repo_path (required), context_lines. Returns: result

git_diff_toolB

Shows differences between branches or commits.

Inputs: repo_path (required), target (required), context_lines. Returns: result

git_diff_unstaged_toolB

Shows changes in the working directory that are not yet staged.

Inputs: repo_path (required), context_lines. Returns: result

git_init_toolB

Initialises a new Git repository at the given path.

Inputs: repo_path (required). Returns: result

git_log_toolB

Shows the commit log of the repository.

Inputs: repo_path (required), max_count. Returns: result

git_optimized_statusA

Fast status check using GitPython β€” shows staged, unstaged, and untracked files.

Preferred over git_status_tool when you only need a quick overview before deciding whether to generate a commit message.

Inputs: repo_path (required). Returns: result

git_reset_toolA

Unstages all staged changes (non-destructive β€” does not discard modifications).

Inputs: repo_path (required). Returns: result

git_show_toolB

Shows the metadata and diff of a specific commit.

Inputs: repo_path (required), revision (required). Returns: result

git_status_toolC

Shows the working tree status.

Inputs: repo_path (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools are clearly distinct, but git_optimized_status and git_status_tool overlap in purpose; however, the description helps differentiate them. Diff tools are separated into staged/unstaged and general, which is clear.

    Naming Consistency4/5

    All tools follow snake_case and most use the git_ prefix, but generate_commit_message lacks the prefix, and git_optimized_status deviates from the verb_noun pattern.

    Tool Count5/5

    15 tools cover the essential Git commit generation workflow without being excessive. Each tool serves a distinct purpose in the pipeline.

    Completeness5/5

    The tool set provides full coverage for generating commits: staging, committing, status checks, diffs, branching, and history. No obvious gaps for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers