Git MCP, the reference server for Git repos on your computer

• Shows what has changed in your working copy

  Lists modified, staged and untracked files in a repository. Use it first to see where things stand before committing.

  Try: “What is the status of my repo at ~/code/app?”

  Files · git_status

• Lists recent commits, with date filters

  Shows commit history with hash, author, date and message, up to a count you set, and optionally between two dates. Use it to see what changed recently.

  Try: “Show the last 10 commits in ~/code/app from the past 2 weeks.”

  Files · git_log

• Shows a commit or a file at a revision

  Displays the contents of a commit, or a file or folder as it was at a given commit, branch or tag. Use it to inspect old versions.

  Try: “Show README.md as it was at tag v1.0.”

  Files · git_show

• Shows edits not yet staged

  Returns the diff of changes in your working directory that are not staged, with a configurable number of context lines.

  Try: “What have I changed but not staged yet?”

  Files · git_diff_unstaged

• Shows edits staged for commit

  Returns the diff of everything currently staged, so you can review what the next commit will contain.

  Try: “Show me what is staged for my next commit.”

  Files · git_diff_staged

• Compares your state with a branch or commit

  Shows the differences between the current state and a branch or commit you name. Use it to review how your work differs from main.

  Try: “Diff my current branch against main.”

  Files · git_diff

• Lists local, remote or all branches

  Lists branches, optionally only those that contain or do not contain a given commit. Use it to find which branches have a fix.

  Try: “List remote branches that contain commit abc1234.”

  Files · git_branch

• Stages files for the next commit

  Adds the files you name to the staging area; passing a dot stages everything. Run it before committing.

  Try: “Stage src/app.py and tests/test_app.py.”

  Write · git_add

• Commits the staged changes

  Records the staged changes as a commit with the message you give and returns the new commit hash. Fails if nothing is staged.

  Try: “Commit the staged changes with the message "Fix login redirect".”

  Write · git_commit

• Unstages everything

  Removes all files from the staging area without discarding your edits. Use it when you staged too much.

  Try: “Unstage everything I added.”

  Write · git_reset

• Creates a new branch

  Creates a branch from the current branch, or from a branch, tag or commit you specify. It does not switch to it.

  Try: “Create a branch called fix-login from main.”

  Write · git_create_branch

• Switches to a branch

  Switches the working copy to another branch. If you give a commit or tag instead, you end up in a detached HEAD state.

  Try: “Switch to the fix-login branch.”

  Write · git_checkout

Watch out for

• It can reach every repo unless you set one

  Without the repository option, every Git repo your account can reach is in scope, for writes too. The README's VS Code and Zed examples leave it out, so add it. github.com

• Older versions could be chained into running code

  Researchers combined older versions with the Filesystem server, using planted text, to run code. Fixed in 2025.12.18, so keep both servers updated. theregister.com

• It changes local history but cannot push

  It can stage, commit, unstage, branch and check out in your working copy. It has no push or network tools, so nothing leaves your machine through it. github.com

• Reference code, not a hardened product

  The maintainers call these servers educational examples, not production-ready. Add your own safeguards. github.com

Security advisories

In their words