init
Initialize a new Git repository
LABSCO SUMMARY
Git stops being a shell the model has to be handed and becomes named operations against a path.
The flags that actually decide what happens are exposed as parameters rather than buried in a command string: force and noVerify on push, track and setUpstream on branch_create, annotated and sign on tag_create, includeUntracked and keepIndex on stash_save. Reading history is not part of this surface — there is no log, diff or blame tool in the list — so it is a writing tool, not an archaeology tool. bulk_action is what keeps a multi-step change from costing a round trip per step.
What it is
A Git front end over 21 operations against a repository path on disk, from init and clone through commits, branches, tags, remotes and stashes.
What you get
- Setup and state: init creates a repository at a path, clone takes a url, status reports the working tree.
- The commit path: add stages named files, commit writes the message, push takes remote, branch, tags, force and noVerify, and pull brings changes back.
- Branches: branch_list, branch_create with track, setUpstream and force, branch_delete, and checkout to switch branches or restore working tree files.
- Tags and remotes: tag_create with annotated, sign and force, tag_list and tag_delete; remote_add with a url, remote_list and remote_remove.
- Stashes: stash_save with message, includeUntracked, keepIndex and all, stash_list, and stash_pop by index.
- bulk_action executes a sequence of operations in one call, the preferred path when a change takes several steps.
Requirements
A repository path on the host — every tool takes one — and a remote url for clone, remote_add, push and pull.
Setup effort
Build from source — git clone https://github.com/Sheshiyer/git-mcp-v2.git
USE CASES
01
Getting a scratch project under version control
Create the repository in place, stage what belongs in it, and take the first commit while checking the working tree between steps.
02
Taking a feature branch from local to review
Cut the branch with its upstream set, switch to it, commit the work, and push it with the flags the remote's hooks require.
03
Parking half-finished work to take a hotfix
Stash what is in progress including the untracked files, switch away to fix the urgent thing, and bring the work back afterwards.
04
Cutting a release tag and getting it to the remote
Create the annotated or signed tag on the commit that ships, confirm it is there, and push it up with the tags flag set.
05
Repointing a checkout at a different remote
Look at what remotes are configured, add the new one with its url, drop the stale one, and pull from where the work now lives.
06
Running a multi-step change without a round trip per step
Put the whole sequence — stage, commit, branch, push — into a single call instead of paying a turn for each operation.
21 tools
Listed in project docs. Your client may show a different list.
clone
Clone a repository
status
Get repository status
add
Stage files
commit
Create a commit
push
Push commits to remote
pull
Pull changes from remote
branch_list
List all branches
branch_create
Create a new branch
branch_delete
Delete a branch
checkout
Switch branches or restore working tree files
tag_list
List tags
tag_create
Create a tag
tag_delete
Delete a tag
remote_list
List remotes
remote_add
Add a remote
remote_remove
Remove a remote
stash_list
List stashes
stash_save
Save changes to stash
stash_pop
Apply and remove a stash
bulk_action
Execute multiple Git operations in sequence. This is the preferred way to execute multiple operations.
BEFORE YOU INSTALL
What to know first
Tools you get
21 tools named in the project's documentation. npx git-mcp-server installs tusharsoni's npm package, not this repository's code, which can only be built from source. Both list the same 21 tools, so they likely share a lineage.
Requires
Node.js and npm, to build and run it
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
21 tool definitions ride along on every turn
INSTALLATION
Connect your client
You clone and build this one yourself, so change the path in the block to wherever your copy ended up, and put your own values in place of the placeholders.
Server setup
TERMINAL
git clone https://github.com/Sheshiyer/git-mcp-v2.git
cd git-mcp-v2
npm install
npm run buildMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"git-v2": {
"command": "node",
"args": [
"path/to/git-mcp-v2/build/index.js"
],
"env": {
"GIT_DEFAULT_PATH": "/path/to/default/git/directory",
"GITHUB_PERSONAL_ACCESS_TOKEN": "your-github-pat"
}
}
}
}Both env values are optional: GIT_DEFAULT_PATH sets a default path for Git operations, and GITHUB_PERSONAL_ACCESS_TOKEN is needed only for GitHub operations. Replace path/to/git-mcp-v2 with the full path to your clone.
