Skip to main content
Glama
deenesjakoruzh
MrOrz

git-commit-aider MCP Server

by MrOrz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Servidor MCP git-commit-aider

Realice confirmaciones de Git en nombre de la IA, para que pueda realizar un seguimiento de la contribución de la IA en su base de código.

Este es un servidor MCP basado en TypeScript que proporciona una herramienta para confirmar cambios programados en un repositorio Git mientras agrega "(aider)" al nombre del confirmador.

Características

Este servidor MCP proporciona solo una herramienta:

commit_staged – Confirma los cambios programados con un mensaje específico.

  • Toma message (cadena, obligatorio) como mensaje de confirmación.

  • Toma cwd (cadena, opcional) para especificar el directorio de trabajo para el comando git.

  • Añade "(aider)" al nombre del confirmador automáticamente.

  • Lee el nombre del confirmador y el correo electrónico de las variables de entorno ( GIT_COMMITTER_NAME , GIT_COMMITTER_EMAIL ) si están configuradas; de lo contrario, recurre a git config user.name y git config user.email .

Con esta herramienta instalada en tu editor de código, puedes indicarle a la IA algo como:

Confirma los cambios por mí

Esto suele suceder después de que la IA ha realizado algunos cambios en su base de código, por lo que a menudo la IA puede proporcionar un buen mensaje de confirmación desde el contexto.

Las confirmaciones con "(aider)" se pueden detectar con el comando aider --stats , que le mostrará la contribución de IA en su base de código.

Related MCP server: Git Polite

Instalación

Para utilizar este servidor, agregue su configuración a su archivo de configuración MCP.

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

La información del confirmador se recupera de:

  1. Variables de entorno GIT_COMMITTER_NAME y GIT_COMMITTER_EMAIL , que siguen la convención de git .

  2. Salida de los comandos git config user.name y git config user.email .

Desarrollo

Instalar dependencias:

npm install

Construir el servidor:

npm run build

Para desarrollo con reconstrucción automática:

npm run watch

Configuración de MCP de ejemplo:

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

(Reemplace /path/to/git-commit-aider con la ruta real a este directorio del servidor).

Depuración

Dado que los servidores MCP se comunican a través de stdio, la depuración puede ser complicada. Recomendamos usar el Inspector MCP , disponible como script de paquete:

npm run inspector

El Inspector proporcionará una URL para acceder a las herramientas de depuración en su navegador.

Available Tools

1 tool
commit_stagedA

Commit staged changes with a specific message, appending "(aider)" to the committer name.

ParametersJSON Schema
NameRequiredDescriptionDefault
messageYesThe commit message.
cwdNoOptional: The working directory for the git command (defaults to the workspace root).

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that the committer name is modified, which is a behavioral side effect. However, without annotations, the description carries the full burden. It could be more explicit about the exact impact (e.g., 'the commit author will be altered'), but the provided detail is adequate for a simple operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence that is front-loaded and contains no wasted words. Every word earns its place, efficiently conveying the core behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple git commit tool with no output schema, the description covers the main action and a notable side effect. However, it omits details like success confirmation or error behavior. Given low complexity, it is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description does not add meaning beyond the schema. Both parameters (message and cwd) are already described in the schema, so the description adds no extra context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool commits staged changes with a message, and specifies a unique behavioral tweak (appending '(aider)' to committer name). The verb and resource are explicit, and with no sibling tools, differentiation is not needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, such as other git commands. Since there are no siblings, the guidance is less critical, but still absent; no prerequisites or limitations are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev1.0.0
    • First observedcommit_staged
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no ambiguity. The tool 'commit_staged' has a clear and distinct purpose.

Naming Consistency5/5

The single tool follows a consistent verb_noun pattern ('commit_staged'), so naming is trivially consistent.

Tool Count2/5

The server has only one tool, which feels thin for a git commit aider. A typical scope would include staging, status, and other related operations.

Completeness2/5

The tool surface is severely incomplete. It only offers commit_staged, missing essential operations like staging, status, branching, or commit management, which will likely cause agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Git Workflow MCP Server

    archis17
    F
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables AI assistants to interact with local Git repositories for operations like status, commits, branching, and diffs, plus GitHub API integration for managing pull requests when authenticated.
    -

  • Git Polite

    uneco
    A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to intelligently organize Git changes into clean, focused commits with autopilot mode or surgical line-by-line staging precision. Supports partial staging of untracked files and handles large diffs with smart truncation.
    5
    1
    MIT

  • AiderMCP

    fuzemobi
    F
    license
    B
    quality
    D
    maintenance
    Enables AI-powered code editing and development tasks through natural language conversations with Claude, using Aider's capabilities for improving code, adding features, fixing bugs, refactoring, and checking status.
    5
    1
    -

Appeared in Searches