zhineng.dev Tools

įŽ€äŊ“中文 | [English]

MCP Git Server

A Model Context Protocol (MCP) server for executing git push operations with flexible branch mapping and pending changes management.

💡 Best Practices

Configure tool prompts to regulate AI's git operation behavior:

  1. Register an account:
  2. Add your own provider and model configuration
  3. Generate an API key
  4. Add to the key's tool prompts:
Tool: get_push
Prompt: Unless I explicitly confirm, do not use native git tools for any operations. Only when I explicitly say to use push pr should you use the git_push and pr tools from MCP tools. At any other time, git-related operations are not allowed.

Tool: save_changes
Prompt: There is a save_changes tool in the tools. You should call this tool to save modification records after completing modifications.

Effect: AI only executes git operations when you explicitly request it, while automatically saving records after each modification.

Features

Installation

npm install -g @liangshanli/mcp-server-git

Environment Variables

Required Variables

Optional Variables

Usage

1. Set Environment Variables

export PROJECT_PATH="/path/to/your/git/repository"
export LOCAL_BRANCH="main"
export REMOTE_BRANCH="main"
export REMOTE_NAME="origin"
export REPO_NAME="my-project"
export TOOL_PREFIX="myproject"

2. Editor Configuration

Create or update .cursor/mcp.json or .vscode/mcp.json in project root:

{
  "mcpServers": {
    "git": {
      "command": "npx",
      "args": ["@liangshanli/mcp-server-git"],
      "env": {
        "PROJECT_PATH": "/path/to/your/git/repository",
        "LOCAL_BRANCH": "main",
        "REMOTE_BRANCH": "main",
        "REMOTE_NAME": "origin",
        "REPO_NAME": "my-project",
        "TOOL_PREFIX": ""
      }
    }
  }
}

3. Start Server

npm start
# or
mcp-server-git
# or (with verification)
npm run start-managed

Multi-Project Instance Support

You can configure multiple Git MCP server instances in your editor to manage different repositories simultaneously.

Cursor Editor Configuration

{
  "mcpServers": {
    "git-web-app": {
      "command": "npx",
      "args": ["@liangshanli/mcp-server-git"],
      "env": {
        "PROJECT_PATH": "D:/projects/web-app",
        "LOCAL_BRANCH": "main",
        "REMOTE_BRANCH": "main",
        "REPO_NAME": "web-app",
        "TOOL_PREFIX": "web"
      }
    },
    "git-api-service": {
      "command": "npx",
      "args": ["@liangshanli/mcp-server-git"],
      "env": {
        "PROJECT_PATH": "D:/projects/api-service",
        "LOCAL_BRANCH": "develop",
        "REMOTE_BRANCH": "develop",
        "REPO_NAME": "api-service",
        "TOOL_PREFIX": "api"
      }
    }
  }
}

VS Code Editor Configuration

{
  "servers": {
    "git-project-a": {
      "command": "npx",
      "args": ["@liangshanli/mcp-server-git"],
      "env": {
        "PROJECT_PATH": "/path/to/project-a",
        "LOCAL_BRANCH": "main",
        "REMOTE_BRANCH": "main",
        "REPO_NAME": "project-a",
        "TOOL_PREFIX": "a"
      }
    },
    "git-project-b": {
      "command": "npx",
      "args": ["@liangshanli/mcp-server-git"],
      "env": {
        "PROJECT_PATH": "/path/to/project-b",
        "LOCAL_BRANCH": "main",
        "REMOTE_BRANCH": "main",
        "REPO_NAME": "project-b",
        "TOOL_PREFIX": "b"
      }
    }
  }
}

Benefits of Multi-Instance Integration:

MCP Tools

git_push

Execute git push with a commit message. Automatically adds and commits changes before pushing.

Important: You must call get_pending_changes first to review changes before using this tool.

Operations performed:

  1. Auto-execute git add . to stage all changes
  2. Auto-execute git commit -m "message" to commit changes
  3. Execute git push to push to remote
  4. Clear all pending changes and reset review status
{
  "name": "git_push",
  "arguments": {
    "message": "Update project files"
  }
}

get_pending_changes

Get and review pending changes before push. Must be called before git_push to enable pushing.

{
  "name": "get_pending_changes",
  "arguments": {
    "limit": 1000
  }
}

save_changes

Save pending changes before push. Records modified files and change content for pre-push review.

{
  "name": "save_changes",
  "arguments": {
    "files": ["src/main.js", "src/utils.js"],
    "content": "Fix bug in user authentication"
  }
}

get_push_history

Get the last 5 push history records to check for duplicates.

get_operation_logs

Get operation logs for debugging.

{
  "name": "get_operation_logs",
  "arguments": {
    "limit": 50
  }
}

git_status

Show status of working directory and staging area.

git_diff

Show differences between working directory and HEAD or staging area.

{
  "name": "git_diff",
  "arguments": {
    "staged": true
  }
}

git_add

Add file contents to staging area.

{
  "name": "git_add",
  "arguments": {
    "files": ["src/main.js", "src/utils.js"]
  }
}

git_log

Show commit history.

{
  "name": "git_log",
  "arguments": {
    "limit": 5,
    "oneline": true
  }
}

git_pull

Execute git pull from configured remote and source branch.

💡 Best Practices and Usage Suggestions

To fully leverage MCP Git Server, follow these "strong constraints" instructions when collaborating with AI:

1. Atomic Recording (save_changes)

Instruction suggestion: "Please call save_changes tool immediately after completing each independent small feature or fixing a bug. You need to explicitly list modified files and briefly describe your modification logic in one or two sentences. Do not accumulate large changes without recording."

Value: This ensures AI's memory fragments are solidified in real-time, preventing loss of initial intent during complex refactoring.

2. Modular Push (git_push)

Instruction suggestion: "When we complete all development and self-testing for the current feature module, please push by calling git_push. Before pushing, you must use get_pending_changes to fully read and summarize all saved records from our conversation, generating a structured Commit Message covering all changes."

Value: Making "summarizing history records" a mandatory prerequisite for push completely eliminates "goldfish brain" commits.

3. Periodic Review

If the session is very long (e.g., lasting several hours), occasionally ask AI to call get_pending_changes for a mid-session summary to ensure stored records perfectly match the current actual code state.

Required Workflow

  1. Make code modifications
  2. Call save_changes to record modification content
  3. Call get_pending_changes to review and mark modifications as reviewed
  4. Call git_push to auto-add, commit and push changes
  5. For subsequent pushes, repeat steps 3-4 (review status resets after each push attempt)

Validation

The server performs the following validations on startup:

  1. Check required environment variables
  2. Verify PROJECT_PATH path exists
  3. Ensure PROJECT_PATH is a valid git repository (contains .git directory)

Related Tools

← Back to MCP Tools List
var _hmt = _hmt || []; (function () { var hm = document.createElement("script"); hm.src = "https://hm.baidu.com/hm.js?ff88834a3841b1795b73b83a590bbbba"; var s = document.getElementsByTagName("script")[0]; s.parentNode.insertBefore(hm, s); })();