Git Commit Aider

🚀 Git Commit Assistant MCP Server

Let AI handle your Git commits and track AI contributions in your codebase.

This is a TypeScript-based MCP server that offers a tool to commit changes in your Git archive on your behalf, appending "(aider)" to the committer's name.

✨ Features

This MCP server provides only one tool:

commit_staged - Commit the archived changes and specify a message.

• Accepts message (string, required) as the commit message.
• Accepts cwd (string, optional) to specify the working directory for Git commands.
• Automatically appends "(aider)" to the committer's name.
• Reads the committer's name and email from environment variables (GIT_COMMITTER_NAME, GIT_COMMITTER_EMAIL). If not set, it falls back to the output of git config user.name and git config user.email.

After installing this tool in your code editor, you can prompt the AI like this:

Commit these changes for me

This usually happens after the AI has made some changes to your codebase, so often the AI can provide a good commit message for you.

Commits with "(aider)" can be detected by the aider --stats command, which will show the AI's contributions in your codebase.

📦 Installation

To use this server, add its configuration to your MCP settings file.

{
  "mcpServers": {
    "git-commit-aider": {
      "command": "npx",
      "args": ["mcp-git-commit-aider"]
    }
  }
}

The committer information is obtained from the following sources:

1. Environment variables GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL, following Git's convention.
2. The output of the git config user.name and git config user.email commands.

🔧 Development

Install dependencies:

npm install

Build the server:

npm run build

Develop with automatic rebuild:

npm run watch

Example MCP configuration:

{
  "mcpServers": {
    "git-commit-aider": {
      "command": "node",
      "args": [
        "/path/to/git-commit-aider/build/index.js"
      ]
    }
  }
}

(Please replace /path/to/git-commit-aider with the actual path.)

🐞 Debugging

Since MCP servers communicate via standard input and output, debugging can be challenging. We recommend using MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access the debugging tools in your browser.