Server facts
git-mcp-server
Project
- Author
- cyanheads
- Repository
- github.com/cyanheads/git-mcp-server
- License
- Apache-2.0
- Category
- Version Control
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 242
- Last commit
- Data as of
Tags
- ai
- enterprise ready
- git
- git server
- git tools
- llm
- mcp
- mcp server
- model context protocol
- modelcontextprotocol
Overview
Git repository maintenance in git-mcp-server spans creating or cloning repositories, inspecting changes, staging files, committing work, and exchanging updates with remotes. Agents can examine authorship and reference history, merge or rebase branches, apply selected commits, and manage stashes, tags, and worktrees. Setting a session directory lets later operations omit repository paths and returns an orientation snapshot covering status, recent history, tags, and remotes. Clearing that setting removes the saved context without restarting the server.
For changelog work, git_changelog_analyze supplies history and review guidance rather than reading the changelog itself; that file must be read separately. The wrap-up tool adds repository context to completion instructions, while the Git Wrap-up prompt guides review, documentation, commits, and tagging. Operators can supply their own wrap-up instructions. Cleanup supports a preview before deletion, and destructive cleanup or hard resets require explicit confirmation. The current provider uses a local Git installation. Commit signing supports GPG or SSH, but signing failures can produce unsigned results with warning information rather than stopping the operation.
git-mcp-server setup notes
- git-mcp-server records stdio only; confirm a network transport upstream before planning remote access.