MCP MGit Server

A MCP server for executing mgit push operations with multiple instance support.

Prerequisites

⚠️ Important: This MCP server requires the MGit tool to be installed and configured on your system.

MGit is a command-line tool for managing multiple Git projects. It helps you efficiently manage, synchronize, and update multiple Git repositories.

MGit Installation and Setup

Before using this MCP server, please:

1. Install MGit: Download and install MGit from https://github.com/liliangshan/mgit/releases

2. Initialize MGit: Follow the MGit setup instructions in the MGit README

3. Configure Projects: Use mgit init to add your Git repositories to MGit

4. Verify Setup: Use mgit list to view available repository names

For detailed MGit usage instructions, features, and configuration, please refer to the MGit README.

Key MGit Features

• Multi-project Management: Manage multiple Git projects with one click

• Multi-language Support: Supports multiple languages including Chinese (Simplified/Traditional), English, Japanese, Korean, French

• Remote Database Sync: Supports project configuration synchronization across multiple devices

• Smart Branch Management: Automatically detects and switches branches to avoid conflicts

• Batch Operations: Supports pulling/pushing changes for multiple projects simultaneously

Features

• ✅ Execute mgit push command for repositories

• ✅ Configurable mgit command (default: mgit)

• ✅ Multiple instance support with repository name isolation

• ✅ Operation logging

• ✅ Error handling and recovery

Installation

Global Installation (Recommended)

Local Installation

From Source

Configuration

Set environment variables:

Usage

1. Direct Run (Global Installation)

2. Using npx (Recommended)

3. Direct Start (Source Installation)

4. Managed Start (Recommended for Production)

Managed start provides:

• Auto-restart (up to 10 times)

• Error recovery

• Process management

• Logging

5. Development Mode

Editor Integration

Cursor Editor Configuration

1. Create .cursor/mcp.json file in your project root:

VS Code Configuration

1. Install the MCP extension for VS Code

2. Create .vscode/settings.json file:

Multiple MGit Server Instances Support

You can configure multiple MGit server instances with different REPO_NAME and PROJECT_NAME to isolate tools and configurations. Each instance must have a unique REPO_NAME (required). This is useful when you need to push to different repositories or manage different project groups. Use mgit list (or ${MGIT_CMD} list) to view available repository names.

Example: Cursor Editor Configuration

Create .cursor/mcp.json file:

Benefits of Multiple Instances:

• Tool Isolation: Each instance has its own tool names (e.g., local_mgit_push, custom_mgit_push)

• Config Isolation: Logs are stored in separate directories (e.g., ./.setting.local/, ./.setting.custom/)

• Different Commands: Configure different mgit commands for each instance

• Project Branding: Each instance can have its own project name for better identification

Note: When using multiple instances, tools will be prefixed with REPO_NAME. For example:

• local-repo_mgit_push - uses local mgit command for local-repo

• custom-repo_mgit_push - uses custom mgit command for custom-repo

As MCP Server

The server communicates with MCP clients via stdin/stdout after startup:

Available Tools

1. mgit_push: Execute mgit push command for the repository configured via REPO_NAME environment variable

   { "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "mgit_push", "arguments": { "message": "Update project files" } } }

2. get_operation_logs: Get operation logs

   { "jsonrpc": "2.0", "id": 3, "method": "tools/call", "params": { "name": "get_operation_logs", "arguments": { "limit": 50, "offset": 0 } } }

Logging

General Logs

Log file location: ./.setting/mcp-mgit.log (or ./.setting.<REPO_NAME>/mcp-mgit.log if REPO_NAME is set)

Logged content:

• All requests and responses

• MGit operation records

• Error messages

• Server status changes

Error Handling

• Individual request errors don't affect the entire server

• Process exceptions are automatically restarted (managed mode)

• Detailed error messages in logs

Environment Variables

Development

Project Structure

Testing

Quick Start

1. Install Package

2. Configure Environment Variables

3. Run Server

Usage Example

Using the mgit_push tool

The mgit_push tool executes the command: ${MGIT_CMD} push ${REPO_NAME} "<message>"

Note: The repository name is configured via the REPO_NAME environment variable (required). Use mgit list (or ${MGIT_CMD} list) to view available repository names.

Parameters:

• message (required): The commit message for the push operation

Example:

If REPO_NAME="my-project" and MGIT_CMD="mgit", this will execute: mgit push my-project "Update documentation"

License

MIT