Provides tools for Git repository interaction and automation, including status, commit, branch, diff, and log operations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-git Show me the status of the current repository."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol server for Git repository interaction and automation. This server provides tools to read, search, and manipulate Git repositories via Large Language Models.
This package is designed to be used as an MCP server with clients like Claude Desktop. Here's how to configure it:
Add this to your MCP client configuration:
{
"mcpServers": {
"git": {
"command": "npx",
"args": ["-y", "mcp-git"]
}
}
}For custom settings:
{
"mcpServers": {
"git": {
"command": "npx",
"args": ["-y", "mcp-git"]
}
}
}Related MCP server: Git Workflow MCP Server
Clone this repository
Install dependencies:
bun installBuild:
bun run buildRun:
bun run startThe server provides these MCP-accessible Git operations:
git_status - Show working tree status
git_init - Initialize new repository
git_log - View commit history (with max_count parameter)
git_diff_unstaged - View unstaged changes
git_diff_staged - View staged changes
git_diff - Compare with branch/commit
git_add - Stage files
git_reset - Unstage changes
git_commit - Create commit
git_create_branch - Create new branch
git_checkout - Switch branches
git_show - View commit contents
Bun v1.2.8 or later
Git installed system-wide
bun run buildbun testPull requests are welcome. For major changes, please open an issue first to discuss proposed changes.
Adds file contents to the staging area
Inputs: repo_path (required), files (required).
Switches branches
Inputs: repo_path (required), branch_name (required).
Records changes to the repository
Inputs: repo_path (required), message (required).
Creates a new branch
Inputs: repo_path (required), branch_name (required), start_point.
Shows differences between branches or commits
Inputs: repo_path (required), target (required).
Shows changes that are staged for commit
Inputs: repo_path (required).
Shows changes in working directory not yet staged
Inputs: repo_path (required).
Initializes a Git repository
Inputs: repo_path (required).
Shows the commit logs
Inputs: repo_path (required), max_count.
Unstages all staged changes
Inputs: repo_path (required).
Shows the contents of a commit
Inputs: repo_path (required), revision (required).
Stashes changes in working directory
Inputs: repo_path (required).
Applies a single stashed state without removing it
Inputs: repo_path (required).
Applies and removes a single stashed state
Inputs: repo_path (required).
Shows the working tree status
Inputs: repo_path (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 15 tools
Every tool has a clearly distinct purpose and targets a different Git operation. There is no ambiguity between tools like git_diff, git_diff_staged, and git_diff_unstaged, or between git_stash, git_stash_apply, and git_stash_pop.
All tools follow the consistent 'git_<verb>' pattern with snake_case. The naming is uniform and predictable, making it easy for an agent to infer tool behavior from its name.
With 15 tools, the server is well-scoped for a Git client. It covers essential operations without being overwhelming or too sparse. Each tool serves a clear purpose in the standard Git workflow.
The tool set covers core local Git operations such as staging, committing, branching, diffing, stashing, and log viewing. However, it lacks tools for remote operations like push, pull, fetch, and merge, which are important for typical Git usage and might require agents to work around.
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
Plain-English git for agents: 22 tools to branch, commit, push and tag. Free tier.
Read and write KukGit repositories, files, issues and pull requests from an AI assistant.
Git-backed platform for skills, tools, and context for AI agents
