Skip to main content
Glama
deenesjakoruzh
MrOrz

git-commit-aider MCP Server

by MrOrz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

git-commit-aider MCP 서버

AI를 대신하여 git 커밋을 수행하면 코드베이스에서 AI 기여도를 추적할 수 있습니다.

이것은 Git 저장소에 단계적 변경 사항을 커밋하고 커미터 이름에 "(aider)"를 추가하는 도구를 제공하는 TypeScript 기반 MCP 서버입니다.

특징

이 MCP 서버는 단 하나의 도구만 제공합니다.

commit_staged - 특정 메시지로 준비된 변경 사항을 커밋합니다.

  • 커밋 메시지로 message (문자열, 필수)를 사용합니다.

  • git 명령의 작업 디렉토리를 지정하려면 cwd (문자열, 선택 사항)를 사용합니다.

  • 커미터 이름에 자동으로 "(aider)"를 추가합니다.

  • GIT_COMMITTER_NAME , GIT_COMMITTER_EMAIL 설정되어 있으면 환경 변수에서 커미터 이름과 이메일을 읽고, 그렇지 않으면 git config user.name 및 git config user.email 로 돌아갑니다.

코드 편집기에 이 도구를 설치하면 다음과 같이 AI에 지시할 수 있습니다.

나를 위해 변경 사항을 커밋해 주세요

이는 일반적으로 AI가 코드베이스에 몇 가지 변경을 한 후에 발생하므로 AI가 컨텍스트에서 적절한 커밋 메시지를 제공할 수 있는 경우가 많습니다.

"(aider)"가 포함된 커밋은 aider --stats 명령으로 검색할 수 있으며, 이 명령을 사용하면 코드베이스에서 AI의 기여도를 확인할 수 있습니다.

Related MCP server: Git Polite

설치

이 서버를 사용하려면 해당 구성을 MCP 설정 파일에 추가하세요.

지엑스피1

커미터 정보는 다음에서 검색됩니다.

  1. GIT_COMMITTER_NAME 및 GIT_COMMITTER_EMAIL 환경 변수는 git 규칙을 따릅니다.

  2. git config user.name 및 git config user.email 명령의 출력.

개발

종속성 설치:

npm install

서버를 빌드하세요:

npm run build

자동 재빌드를 사용한 개발의 경우:

npm run watch

샘플 MCP 구성:

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

( /path/to/git-commit-aider 이 서버 디렉토리의 실제 경로로 바꾸세요.)

디버깅

MCP 서버는 stdio를 통해 통신하므로 디버깅이 어려울 수 있습니다. 패키지 스크립트로 제공되는 MCP Inspector를 사용하는 것이 좋습니다.

npm run inspector

검사기는 브라우저에서 디버깅 도구에 액세스할 수 있는 URL을 제공합니다.

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