cyanheads/git-mcp-server

Empower your AI agents with comprehensive, secure, and programmatic control over Git repositories!

An MCP (Model Context Protocol) server providing a robust, LLM-friendly interface to the standard git command-line tool. Enables LLMs and AI agents to perform a wide range of Git operations like clone, commit, push, pull, branch, diff, log, status, and more via the MCP standard.

Built on the cyanheads/mcp-ts-template, this server follows a modular architecture with robust error handling, logging, and security features.

This server equips your AI with a comprehensive suite of tools to interact with Git repositories:

| Overview | Features | Installation | | Configuration | Project Structure | | Tools | Resources | Development | License |

The Git MCP Server acts as a bridge, allowing applications (MCP Clients) that understand the Model Context Protocol (MCP) – like advanced AI coding assistants (LLMs), IDE extensions, or custom research tools – to interact directly and safely with local Git repositories.

Instead of complex scripting or manual command-line interaction, your tools can leverage this server to:

• Automate Git workflows: Clone repositories, create branches, stage changes, commit work, push updates, and manage tags programmatically.
• Gain repository insights: Check status, view logs, diff changes, and inspect Git objects without leaving the host application.
• Integrate Git into AI-driven development: Enable LLMs to manage version control as part of their coding or refactoring tasks, ensuring code integrity and history.
• Support CI/CD and DevOps automation: Build custom scripts and tools that orchestrate complex Git operations for automated builds, testing, and deployments.

Built on the robust mcp-ts-template, this server provides a standardized, secure, and efficient way to expose Git functionality via the MCP standard. It achieves this by securely executing the standard git command-line tool installed on the system using Node.js's child_process module, ensuring compatibility and leveraging the full power of Git.

Developer Note: This repository includes a .clinerules file that serves as a developer cheat sheet for your LLM coding agent with quick reference for the codebase patterns, file locations, and code snippets.

Leverages the robust utilities provided by the mcp-ts-template:

• Logging: Structured, configurable logging (file rotation, stdout JSON, MCP notifications) with sensitive data redaction.
• Error Handling: Centralized error processing, standardized error types (McpError), and automatic logging.
• Configuration: Environment variable loading (dotenv) with comprehensive validation.
• Input Validation/Sanitization: Uses zod for schema validation and custom sanitization logic (crucial for paths).
• Request Context: Tracking and correlation of operations via unique request IDs using AsyncLocalStorage.
• Type Safety: Strong typing enforced by TypeScript and Zod schemas.
• HTTP Transport: High-performance HTTP server using Hono, featuring session management, CORS, and authentication support.
• Deployment: Multi-stage Dockerfile for creating small, secure production images with native dependency support.

• Direct Git CLI Execution: Interacts with Git by securely executing the standard git command-line tool via Node.js child_process, ensuring full compatibility and access to Git's features.
• Comprehensive Command Coverage: Exposes a wide range of Git commands as MCP tools (see Tools section).
• Repository Interaction: Supports status checking, branching, staging, committing, fetching, pulling, pushing, diffing, logging, resetting, tagging, and more.
• Working Directory Management: Allows setting and clearing a session-specific working directory for context persistence across multiple Git operations.
• Safety Features: Includes checks and requires explicit confirmation for potentially destructive operations like git clean and git reset --hard.
• Commit Signing: Supports GPG or SSH signing for verified commits, controlled via the GIT_SIGN_COMMITS environment variable and server-side Git configuration. Includes an optional tool parameter to fall back to unsigned commits on signing failure.

• Node.js (>=20.0.0)
• npm (comes with Node.js)
• Git installed and accessible in the system PATH.

Add the following to your MCP client's configuration file (e.g., cline_mcp_settings.json). This configuration uses npx to run the server, which will automatically install the package if not already present:

{
  "mcpServers": {
    "git-mcp-server": {
      "command": "npx",
      "args": ["@cyanheads/git-mcp-server"],
      "env": {
        "MCP_LOG_LEVEL": "info",
        "GIT_SIGN_COMMITS": "false"
      }
    }
  }
}

npm install @cyanheads/git-mcp-server

1. Clone the repository:

   git clone https://.com/cyanheads/git-mcp-server.git
   cd git-mcp-server

2. Install dependencies:

   npm install

3. Build the project:

   npm run build
   # or npm run rebuild

Configure the server using environment variables. These environmental variables are set within your MCP client config/settings (e.g. claude_desktop_config.json for Claude Desktop)

The codebase follows a modular structure within the src/ directory:

src/
├── index.ts           # Entry point: Initializes and starts the server
├── config/            # Configuration loading (env vars, package info)
│   └── index.ts
├── mcp-server/        # Core MCP server logic and capability registration
│   ├── server.ts      # Server setup, capability registration
│   ├── transports/    # Transport handling (stdio, http)
│   ├── resources/     # MCP Resource implementations (currently none)
│   └── tools/         # MCP Tool implementations (subdirs per tool)
├── types-global/      # Shared TypeScript type definitions
└── utils/             # Common utility functions (logger, error handler, etc.)

For a detailed file tree, run npm run tree or see docs/tree.md.

The Git MCP Server provides a suite of tools for interacting with Git repositories, callable via the Model Context Protocol.

Note: The path parameter for most tools defaults to the session's working directory if set via git_set_working_dir.

MCP Resources are not implemented in this version (v2.1.4).

This version focuses on the refactored Git tools implementation based on the latest mcp-ts-template and MCP SDK v1.13.0. Resource capabilities, previously available, have been temporarily removed during this major update.

If you require MCP Resource access (e.g., for reading file content directly via the server), please use the stable v1.2.4 release.

Future development may reintroduce resource capabilities in a subsequent release.

# Build the project (compile TS to JS in dist/ and make executable)
npm run build

# Test the server locally using the MCP inspector tool (stdio transport)
npm run inspector

# Test the server locally using the MCP inspector tool (http transport)
npm run inspector:http

# Clean build artifacts
npm run clean

# Generate a file tree representation for documentation
npm run tree

# Clean build artifacts and then rebuild the project
npm run rebuild

# Format code with Prettier
npm run format

# Start the server using stdio (default)
npm start
# Or explicitly:
npm run start:stdio

# Start the server using HTTP transport
npm run start:http

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.