Git Commit Aider

A simple MCP server that makes git commits on behave of AI, so that you can track AI contribution in your codebase

javascript

8

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mrorz-mcp-git-commit-aider": {
      "command": "npx",
      "args": [
        "mcp-git-commit-aider"
      ],
      "env": {
        "GIT_COMMITTER_NAME": "YOUR_NAME_OR_EMPTY",
        "GIT_COMMITTER_EMAIL": "YOUR_EMAIL_OR_EMPTY"
      }
    }
  }
}

You deploy a dedicated MCP server that lets AI-generated changes be committed in your Git repository by appending a marker to the committer name. This enables you to track AI contributions while keeping your normal commit workflow intact.

How to use

Connect this MCP server to your editor or IDE client to enable a dedicated tool for committing staged changes. When you prompt the AI with a request like “Commit the changes for me,” the server runs and creates a standard Git commit in your repository with a committer name that includes "(aider)". The committer email and name are taken from environment variables if set, or from your local Git configuration if not. Use this workflow to clearly separate AI-driven commits from human-driven ones and to generate meaningful commit messages.

How to install

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

Notes on usage and configuration

_committer identity_ is determined as follows: if your environment defines GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL, those values are used. Otherwise, the server uses the outputs of git config user.name and git config user.email. The AI marker "(aider)" is appended to the committer name automatically to mark AI-generated commits.

Security considerations

Only enable this MCP server in trusted environments where commit messages and access to the repository are carefully controlled. The server reads committer identity from environment variables or Git configuration. Do not expose these capabilities to untrusted scripts or editors.

Troubleshooting

If commits are created without the AI marker, verify that the environment variables GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL are set. If they are not, ensure Git user.name and user.email are configured in your local repository. Check that the server command is accessible as shown in the installation step and that your editor is wired to invoke the MCP tool correctly.

Advanced usage and alternatives

If you prefer to amend the author after a commit instead of using the MCP, you can run a standard Git command to adjust the last commit's author to include the AI marker. You can also set up a Git alias to simplify this process for repetitive use.

Example workflow

Stage changes in your repository. 2) Trigger the MCP server via your editor’s AI commit prompt. 3) Observe that a commit is created with the committer name appended by "(aider)" and with your chosen message.

Tool overview

commit_staged — Commit staged changes with a specific message and automatically append "(aider)" to the committer name. The tool accepts a required message and an optional cwd to set the working directory for Git operations.

Available tools

commit_staged

Commit staged changes with a provided message and automatically append "(aider)" to the committer name.