Git MCP Server
Git repositories accessed and manipulated through AI-driven automation workflows.
Data last scanned 2 days ago · Reviewed 2 months ago
Overview
This server provides tools to integrate Git version control directly into Large Language Model workflows. It allows for the inspection of repository states, viewing unstaged and staged changes, and comparing differences between branches or specific commits. Users can perform essential repository management tasks, including staging files, committing changes, and resetting the index. Built in TypeScript, the server facilitates interaction with local Git repositories via standardized tools. It includes comprehensive log filtering capabilities, supporting ISO 8601 timestamps and relative date queries to help developers track repository history effectively.
Our verdict
With a security score of 56/100, this server is currently classified as high risk. The primary security concern is the total lack of authentication, meaning any process with access to the configuration can execute commands on your repositories. Furthermore, the absence of a read-only mode means every installation inherently grants full write access to your files. It should only be used in trusted, local development environments where you are comfortable with the AI having unrestricted permission to modify your git state.
- Maintained by the official modelcontextprotocol organization
- Zero direct dependencies minimize the software supply chain surface
- Active development with commits within the last five days
- No authentication mechanism implemented for configuration access
- Lacks read-only mode, exposing every repository to full write access
- License status is marked as NOASSERTION
- Explicitly described as being in early development stages
Tools
| Tool | Description | Risk |
|---|---|---|
| git_status | Shows the working tree status | low |
| git_diff_unstaged | Shows changes in working directory not yet staged | low |
| git_diff_staged | Shows changes that are staged for commit | low |
| git_diff | Shows differences between branches or commits | low |
| git_commit | Records changes to the repository | medium |
| git_add | Adds file contents to the staging area | medium |
| git_reset | Unstages all staged changes | medium |
| git_log | Shows the commit logs with optional date filtering | low |
| git_create_branch | Creates a new branch | medium |
| git_checkout | Switches branches | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What methods are available to install this Git MCP server?
You can use uvx to run the server directly without specific installation, or you can install it via pip using 'pip install mcp-server-git'.
›How can I configure the server to work with Claude Desktop?
You need to add the server configuration to your claude_desktop_config.json file under the mcpServers key, specifying the command and arguments for either uvx, Docker, or a standard python installation.
›Can I filter commit logs by date?
Yes, the git_log tool supports optional start_timestamp and end_timestamp parameters, which accept ISO 8601, absolute, or relative date formats.
›Are the tools in this server finalized?
No, the Git MCP server is currently in early development, so available tools and functionality are subject to change and expansion.
›What information is required to use the diff tools?
All diff tools require a repo_path, and some allow an optional context_lines parameter to define how many lines of context to display.
Alternatives
Badge
Maintain this server? Add the live badge to your README.