Git MCP Server (Casey Hand)
Git repository operations and history analysis through twenty-eight specialized tools.
Data last scanned today · Reviewed today
Overview
This TypeScript-based MCP server provides AI agents with comprehensive control over local Git environments. It exposes twenty-eight distinct tools categorized into areas like repository management, staging, committing, history inspection, and branching workflows. Designed to handle both STDIO and streamable HTTP communication, the server includes specialized functions for tasks such as rebase, cherry-pick, and automated changelog analysis. It leverages the latest MCP SDK standards to allow AI models to interact directly with version control systems.
Our verdict
With a high-risk security score of 43/100, this tool is currently intended for evaluation in non-sensitive environments. The risk classification is largely driven by the lack of an editorially reviewed authentication method and the fact that read-only mode capabilities remain unverified. As a community-maintained project, it lacks the oversight of an official vendor-backed server, making it best suited for developers building personal AI-assisted Git workflows rather than mission-critical infrastructure.
- Supports 28 distinct Git operations via seven functional categories
- Contains only three direct dependencies to minimize supply-chain surface
- Maintained under the permissive Apache-2.0 open-source license
- Provides specific tools for automated changelog analysis
- Security score of 43/100 indicates significant high-level risks
- Authentication methods have not yet been editorially reviewed
- Read-only mode functionality lacks verification
- Maintained by community contributors rather than an official vendor
Setup
{
"mcpServers": {
"cyanheads-git-mcp-server": {
"args": [
"-y",
"@cyanheads/git-mcp-server"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| git_init | Initialize repos | medium |
| git_clone | clone from remotes | medium |
| git_status | check status | low |
| git_clean | clean untracked files | high |
| git_add | Stage changes | medium |
| git_commit | create commits | medium |
| git_diff | compare changes | low |
| git_log | View commit history | low |
| git_show | inspect objects | low |
| git_blame | trace authorship | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What runtimes are supported for this server?
The server runs on both Node.js (version 20.0.0 or higher) and Bun (version 1.2.0 or higher), with the runtime being automatically detected.
›Can I use this server with different transport protocols?
Yes, the server supports both stdio and Streamable HTTP transport modes, which you can configure using the MCP_TRANSPORT_TYPE environment variable.
›How do I set the working directory for my Git operations?
You can use the git_set_working_dir tool to define the directory for your current session, which is accessible via the git://working-directory resource.
›Are there specific environment variables I must configure?
Yes, you should provide git identity settings including GIT_USERNAME, GIT_EMAIL, and GIT_SIGN_COMMITS, alongside configuration for your base directory and log directory.
Badge
Maintain this server? Add the live badge to your README.