GIT MCP Server

Created By
wty0512a year ago
A Model Context Protocol (MCP) server to provide git tools for LLM Agents, with fixes for the amend parameter caching issue
Overview

what is GIT MCP Server?

GIT MCP Server is a Model Context Protocol (MCP) server designed to provide Git tools for LLM Agents, enabling them to manage Git repositories without direct filesystem or command-line access.

how to use GIT MCP Server?

To use GIT MCP Server, install it via NPM or from source, then run the server using the command git-mcp-server. It communicates through stdin/stdout using the Model Context Protocol, making it compatible with any MCP client.

key features of GIT MCP Server?

  • Repository management including initialization, cloning, and status checks.
  • Branch operations such as creating, listing, checking out, and merging branches.
  • Working directory operations including staging files, committing changes, and creating diffs.
  • Remote operations for adding, fetching, pulling, and pushing to remote repositories.
  • Advanced Git commands like managing tags, stashing changes, and rebasing branches.

use cases of GIT MCP Server?

  1. Enabling AI assistants to perform Git operations seamlessly.
  2. Integrating with other MCP clients for enhanced Git management.
  3. Providing a standardized interface for Git operations in various applications.

FAQ from GIT MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows for standardized communication between AI agents and services.

  • How do I install GIT MCP Server?

You can install it via NPM using npm install -g git-mcp-server or clone the repository and build it from source.

  • Is GIT MCP Server free to use?

Yes! GIT MCP Server is open-source and free to use under the Apache License 2.0.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wty0512
Star
0
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago