Git MCP

Name: Git MCP
Author: selfagency

by selfagencyversion 0.4.2i★ 1iRuns on your computer

Registry nameio.github.selfagency/git-mcp

How to install

What it does

A Git MCP server that doesn't suck

Connects Runs on your computer
Account or key Needs GIT_SIGNING_KEY
Category Developer tools

Install

Pick the AI app you use, then copy the settings.

Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

ClaudeWeb · app · phoneChatGPTWebClaude CodeTerminalCursorCode editorVS CodeCode editorOtherOther apps

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Git MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Sign up and create a Git MCP key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Done
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Done

Paste these settings and save the file

{
  "mcpServers": {
    "git": {
      "command": "npx",
      "args": [
        "-y",
        "@selfagency/git-mcp"
      ],
      "env": {
        "GIT_SIGNING_KEY": "your-value"
      }
    }
  }
}

Paste the key only into the app’s field, never into a chat or to anyone

Done

Quit Claude and open it again
Done
Try it
Use Git MCP and tell me what you can do for me, then show me one thing
✓ If Claude says it is using Git MCP or shows a Git MCP tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

GIT_REPO_PATH Default repository path for all tool requests. Can also be set via the --repo / --repo-path CLI argument. If omitted, each tool call must supply repo_path explicitly.
GIT_ALLOW_NO_VERIFY Set to 'true' to expose a no_verify parameter on commit and push tools, passing --no-verify to Git and bypassing pre-commit / pre-push hooks.
GIT_ALLOW_FORCE_PUSH Set to 'true' to expose a force parameter on push tools. Remote branch protection rules (GitHub/GitLab) are still enforced server-side regardless.
GIT_ALLOW_FLOW_HOOKS Set to 'true' to allow git_flow to execute git-flow-next-compatible hook and filter programs discovered from git config or repository hook locations.
GIT_SIGNING_FORMAT Signing format for commits and tags. Accepted values: openpgp, ssh, x509.
GIT_AUTO_SIGN_COMMITS Set to 'true' to automatically sign all commits produced by this server.
GIT_AUTO_SIGN_TAGS Set to 'true' to automatically sign all tags produced by this server.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Git MCP yet

Git MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Git MCP

Steps for Claude →You need a Git MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Steps for Claude Code →You need a Git MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Steps for Cursor →You need a Git MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Steps for VS Code →You need a Git MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Sentry✓ ChatGPT
Compiler Explorer✓ ChatGPT
GitDiagram✓ ChatGPT

Works with Claude Code, with some setup first

You need a Git MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Sign up and create a Git MCP key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Done
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Done
4
Paste this command and press Enter
```
claude mcp add --scope user git --env GIT_SIGNING_KEY=your-value -- npx -y @selfagency/git-mcp
```
Replace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
Done
Type /mcp in Claude Code
You should see Git MCP listed as connected
Done
Try it
Use Git MCP and tell me what you can do for me, then show me one thing
✓ If Claude Code says it is using Git MCP or shows a Git MCP tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

GIT_REPO_PATH Default repository path for all tool requests. Can also be set via the --repo / --repo-path CLI argument. If omitted, each tool call must supply repo_path explicitly.
GIT_ALLOW_NO_VERIFY Set to 'true' to expose a no_verify parameter on commit and push tools, passing --no-verify to Git and bypassing pre-commit / pre-push hooks.
GIT_ALLOW_FORCE_PUSH Set to 'true' to expose a force parameter on push tools. Remote branch protection rules (GitHub/GitLab) are still enforced server-side regardless.
GIT_ALLOW_FLOW_HOOKS Set to 'true' to allow git_flow to execute git-flow-next-compatible hook and filter programs discovered from git config or repository hook locations.
GIT_SIGNING_FORMAT Signing format for commits and tags. Accepted values: openpgp, ssh, x509.
GIT_AUTO_SIGN_COMMITS Set to 'true' to automatically sign all commits produced by this server.
GIT_AUTO_SIGN_TAGS Set to 'true' to automatically sign all tags produced by this server.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Git MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Sign up and create a Git MCP key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Done
Click this button to open Cursor
Open in Cursor
Cursor asks you to confirm; click Install
Done
Fill in your key
In the Git MCP settings, GIT_SIGNING_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Done
Open the AI chat in Cursor in Agent mode
Done
Try it
Use Git MCP and tell me what you can do for me, then show me one thing
✓ If Cursor says it is using Git MCP or shows a Git MCP tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

GIT_REPO_PATH Default repository path for all tool requests. Can also be set via the --repo / --repo-path CLI argument. If omitted, each tool call must supply repo_path explicitly.
GIT_ALLOW_NO_VERIFY Set to 'true' to expose a no_verify parameter on commit and push tools, passing --no-verify to Git and bypassing pre-commit / pre-push hooks.
GIT_ALLOW_FORCE_PUSH Set to 'true' to expose a force parameter on push tools. Remote branch protection rules (GitHub/GitLab) are still enforced server-side regardless.
GIT_ALLOW_FLOW_HOOKS Set to 'true' to allow git_flow to execute git-flow-next-compatible hook and filter programs discovered from git config or repository hook locations.
GIT_SIGNING_FORMAT Signing format for commits and tags. Accepted values: openpgp, ssh, x509.
GIT_AUTO_SIGN_COMMITS Set to 'true' to automatically sign all commits produced by this server.
GIT_AUTO_SIGN_TAGS Set to 'true' to automatically sign all tags produced by this server.

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Git MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Install Node.js
One time only; it works for every server that needs Node.js
Open the Node.js download page ↗
Done
Sign up and create a Git MCP key
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Done
Click this button to open VS Code
Open in VS Code
VS Code asks you to confirm; click Install
Done
Fill in your key
In the Git MCP settings, GIT_SIGNING_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Done
Open the AI chat in VS Code in Agent mode
Done
Try it
Use Git MCP and tell me what you can do for me, then show me one thing
✓ If VS Code says it is using Git MCP or shows a Git MCP tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

GIT_REPO_PATH Default repository path for all tool requests. Can also be set via the --repo / --repo-path CLI argument. If omitted, each tool call must supply repo_path explicitly.
GIT_ALLOW_NO_VERIFY Set to 'true' to expose a no_verify parameter on commit and push tools, passing --no-verify to Git and bypassing pre-commit / pre-push hooks.
GIT_ALLOW_FORCE_PUSH Set to 'true' to expose a force parameter on push tools. Remote branch protection rules (GitHub/GitLab) are still enforced server-side regardless.
GIT_ALLOW_FLOW_HOOKS Set to 'true' to allow git_flow to execute git-flow-next-compatible hook and filter programs discovered from git config or repository hook locations.
GIT_SIGNING_FORMAT Signing format for commits and tags. Accepted values: openpgp, ssh, x509.
GIT_AUTO_SIGN_COMMITS Set to 'true' to automatically sign all commits produced by this server.
GIT_AUTO_SIGN_TAGS Set to 'true' to automatically sign all tags produced by this server.

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Git MCP💬 Discussion →

For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user git --env GIT_SIGNING_KEY=your-value -- npx -y @selfagency/git-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "git": {
      "command": "npx",
      "args": [
        "-y",
        "@selfagency/git-mcp"
      ],
      "env": {
        "GIT_SIGNING_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "git": {
      "command": "npx",
      "args": [
        "-y",
        "@selfagency/git-mcp"
      ],
      "env": {
        "GIT_SIGNING_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "git": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@selfagency/git-mcp"
      ],
      "env": {
        "GIT_SIGNING_KEY": "your-value"
      }
    }
  }
}

Values you fill in

GIT_REPO_PATH env
Default repository path for all tool requests. Can also be set via the --repo / --repo-path CLI argument. If omitted, each tool call must supply repo_path explicitly.
GIT_ALLOW_NO_VERIFY env
Set to 'true' to expose a no_verify parameter on commit and push tools, passing --no-verify to Git and bypassing pre-commit / pre-push hooks.
GIT_ALLOW_FORCE_PUSH env
Set to 'true' to expose a force parameter on push tools. Remote branch protection rules (GitHub/GitLab) are still enforced server-side regardless.
GIT_ALLOW_FLOW_HOOKS env
Set to 'true' to allow git_flow to execute git-flow-next-compatible hook and filter programs discovered from git config or repository hook locations.
GIT_SIGNING_KEY secret required env
Default signing key: a GPG key ID, an SSH public key path, or empty to use git's configured user.signingkey. Used when GIT_AUTO_SIGN_COMMITS or GIT_AUTO_SIGN_TAGS is enabled.
GIT_SIGNING_FORMAT env
Signing format for commits and tags. Accepted values: openpgp, ssh, x509.
GIT_AUTO_SIGN_COMMITS env
Set to 'true' to automatically sign all commits produced by this server.
GIT_AUTO_SIGN_TAGS env
Set to 'true' to automatically sign all tags produced by this server.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub stars i: 1
Downloads per weeki: 118/wk
Licence i: No licence stated
Connection: Runs on your computer
Transport: stdio
Latest versioni: 0.4.2
Categoryi: Developer tools
Published to registryi: Oct 14, 2026
Code last changedi: Oct 14, 2026
Maker: selfagency
Packages: npm: @selfagency/git-mcp
Repo: voxslopuli/git-mcp
Registry status: Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 14, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account voxslopuli, which owns the repo
✓ Pass
Still maintained
Code last changed 31 days ago
✕ Fail
Has a licence
No licence file found in the repo
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

User reviews

No reviews yet

Compared with others in Developer toolsi

More stars than 69% of the other 5866 servers in this category
Published to the registry more recently than 50% of the other 5866 servers in this category
Basic checks equal to or better than 45% of the other 5866 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Git MCP safe?

It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GIT_SIGNING_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 31 days ago, and the latest version (0.4.2) reached the registry 31 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: REA, GitHub, Serena MCP: the IDE for your agent

Others in the same category

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 455.4KUpdated 2 days ago

Runs on your computer

Install

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.4KUpdated 11 days ago

Computer or cloud

Install

Serena MCP: the IDE for your agent

A powerful toolkit for coding, providing semantic retrieval and editing capabilities.

by oraiosWidely used↓ 35.2K/wk★ 31.3KUpdated 6 months ago

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

git-mcp

A Git MCP server that doesn't suck

Exposes the full Git workflow to any MCP-compatible AI agent — inspect, write, branch, remote, stash, rebase, LFS, git-flow, documentation lookup, and more. Designed to be safe by default, composable, and fast. Powered by simple-git.

Built for coding agents in tools like GitHub Copilot, Claude Code, Cursor, and OpenAI Codex, while remaining compatible with any MCP client that can call tools and resources.

Features

18 tools with 80+ actions covering everyday Git workflows, advanced recovery, history rewriting, repository analytics, forge pull requests, and external VCS awareness
Safety-first — destructive operations require explicit confirmation; force push and hook bypass are opt-in via server config
GPG/SSH signing for commits and tags, with server-level auto-sign support
Git LFS — track patterns, manage objects, install hooks, migrate history
Git Flow — drives the git-flow-next CLI, so the finish state machine, conflict recovery, and worktree lifecycle stay correct as the CLI evolves. Preset init, overview, config CRUD, generalized topic actions, and classic feature/release/hotfix/support aliases
Documentation lookup — search git-scm.com and fetch man pages directly from the LLM
MCP Resources — URI-addressable read-only views of status, log, branches, and diff
Bundled agent skill — skills/git-mcp-workflow/ documents MCP-first Git workflows, recovery, worktrees, releases, and advanced operations for AI agents and coding agents; installable via skills-npm and skill.sh
External VCS awareness — git_but_check / git_jj_check detect GitButler and Jujutsu and guide agents to prefer their native CLIs/MCP (with but teardown guidance) over git-mcp tools when appropriate
History rewrite — git_rewrite: reword, squash, rewrite-messages, and backup/restore for safe commit-history rewriting
Repository analytics — git_analytics: contributors, churn, activity, summary, and file-stats computed from local git history
Pull requests — git_pr: create/list/merge PRs/MRs on GitHub, GitLab, Forgejo, Gitea, and Bitbucket via provider CLI or REST API
Tangled & Entire awareness — git_tangled_check / git_entire_check detect Tangled hosting and Entire session/context management
Multi-repo — pass repo_path per-call or configure a server-level default
Worktrees — git_worktree: plain git worktree by path, or branch-addressed worktrees via git flow worktree with path templates and provenance-aware cleanup
Cross-platform — macOS, Linux, Windows (Git for Windows), all covered by CI

Quick Start

npx (no install)

npx @selfagency/git-mcp --repo-path /path/to/your/repo

Install globally

npm install -g @selfagency/git-mcp

git-mcp --repo-path /path/to/your/repo

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

"mcpServers": { "git": { "command": "npx", "args": ["-y", "@selfagency/git-mcp", "--repo-path", "/path/to/your/repo"] } } }

VS Code (Copilot)

Add to .vscode/mcp.json in your project:

"servers": { "git": { "command": "npx", "args": ["-y", "@selfagency/git-mcp", "--repo-path", "${workspaceFolder}"] } } }

Configuration

All configuration is via environment variables. Pass them in your MCP client config:

Variable	Default	Description
`GIT_REPO_PATH`	—	Default repository path (also: `--repo-path` CLI arg)
`GIT_ALLOW_NO_VERIFY`	`false`	Allow `--no-verify` on commit/push (bypasses hooks)
`GIT_ALLOW_FORCE_PUSH`	`false`	Allow `--force` on push
`GIT_ALLOW_FLOW_HOOKS`	`false`	Allow `git_flow` hooks and filters to execute
`GIT_AUTO_SIGN_COMMITS`	`false`	Automatically sign every commit
`GIT_AUTO_SIGN_TAGS`	`false`	Automatically sign every tag
`GIT_SIGNING_KEY`	—	Default GPG key ID or SSH key path
`GIT_SIGNING_FORMAT`	—	Signing format: `openpgp`, `ssh`, or `x509`
`GIT_ALLOW_BUT`	`false`	Enable GitButler awareness (`git_but_check`)
`GIT_ALLOW_JJ`	`false`	Enable Jujutsu awareness (`git_jj_check`)
`GIT_ALLOW_TANGLED`	`false`	Enable Tangled awareness (`git_tangled_check`)
`GIT_ALLOW_ENTIRE`	`false`	Enable Entire awareness (`git_entire_check`)
`BUT_BINARY`	`but`	Override the `but` executable path
`JJ_BINARY`	`jj`	Override the `jj` executable path
`ENTIRE_BINARY`	`entire`	Override the `entire` executable path
`GITHUB_TOKEN`	—	GitHub token for `git_pr` REST fallback
`GITLAB_TOKEN`	—	GitLab token for `git_pr` REST fallback
`FORGEJO_TOKEN`	—	Forgejo/Gitea token for `git_pr` REST fallback
`BITBUCKET_TOKEN`	—	Bitbucket token for `git_pr` REST fallback
`GIT_FORGE_PROVIDER`	—	Explicit forge provider for self-hosted instances

Tool Reference

Tools are grouped by domain. Each root tool takes an action parameter that selects the operation. Where an action is marked as default, omitting action will use it.

Context (`git_context`)

Action	Description
`summary`	_(default)_ Full repo snapshot: branch, upstream, pending changes, in-progress operations
`search`	Search commit history and working tree content
`get_config`	Read a Git config value
`set_config`	Write a Git config value
`aliases`	List all configured git aliases

Status (`git_status`)

Action	Description
`status`	_(default)_ Working tree and branch status
`diff`	Unstaged, staged, or ref-to-ref diff
`diff_main`	Changes from branch divergence point vs `main` (or configurable base branch)

History (`git_history`)

Action	Description
`log`	_(default)_ Commit log with filtering, pagination, revision ranges, and pathspecs
`show`	Inspect a single commit
`blame`	Line-by-line attribution for a file
`reflog`	Full reflog — the recovery ledger
`lg`	Compact graph log (`--oneline --graph --decorate --all`)
`who`	Contributor shortlog (supports optional `file_path`)

Commits (`git_commits`)

Action	Description
`add`	Stage files or hunks
`restore`	Discard working tree changes
`unstage`	Remove files from the staging area
`commit`	Create a commit with message, signing, and author flags
`amend`	Amend the last commit without editing the message
`wip`	Stage all changes and commit with message `WIP`
`revert`	Create a revert commit for a given ref
`undo`	Soft-reset the last commit (`reset --soft HEAD~1`)
`reset`	Reset HEAD with configurable mode (soft/mixed/hard)
`nuke`	Hard-reset the last commit — requires `confirm=true`

Branches (`git_branches`)

Action	Description
`list`	_(default)_ Local and remote branch listing
`create`	Create a branch
`delete`	Delete a branch
`rename`	Rename a branch
`checkout`	Switch to a branch or ref
`set_upstream`	Set or update tracking upstream
`recent`	Recent branches sorted by committer date

Remotes (`git_remotes`)

Action	Description
`list`	_(default)_ List configured remotes
`manage`	Add, remove, or rename a remote
`fetch`	Fetch from a remote
`pull`	Pull (fetch + merge/rebase)
`push`	Push to a remote; `force_with_lease` supported

Workspace (`git_workspace`)

Action	Description
`stash`	Stash and pop/apply/drop/list/show stash entries
`stash_all`	Stash tracked and untracked changes in one operation
`rebase`	Start, continue, abort, or skip a rebase
`cherry_pick`	Apply one or more commits; supports continue/abort/skip
`merge`	Merge branches with full flag control
`bisect`	Binary search for a regression (start, good, bad, reset, log)
`tag`	Create, list, delete, or push tags; supports GPG/SSH signing
`worktree`	Add, list, remove, lock, unlock, prune, or repair linked worktrees
`submodule`	Add, update, sync, init, deinit, and list submodules

Git Flow (`git_flow`)

Drives the git-flow-next CLI, which must be installed and on PATH (brew install git-flow-next, or the releases page). Set GIT_FLOW_BINARY to override the path. When the binary is missing, the tool returns an install hint rather than failing opaquely.

Operation	Description
`init`	Initialize a repository with git-flow branch conventions

| overview | Show the current flow state and act

Only the beginning is shown; read the rest in the repo

Git MCP

What it does

Install

Install Node.js

Sign up and create a Git MCP key

Open the Claude desktop app’s settings file

Paste these settings and save the file

Quit Claude and open it again

Try it

What you can do instead

Install Node.js

Sign up and create a Git MCP key

Open Terminal

Paste this command and press Enter

Type /mcp in Claude Code

Try it

Install Node.js

Sign up and create a Git MCP key

Click this button to open Cursor

Fill in your key

Open the AI chat in Cursor in Agent mode

Try it

Install Node.js

Sign up and create a Git MCP key

Click this button to open VS Code

Fill in your key

Open the AI chat in VS Code in Agent mode

Try it

Installed on your computer

Values you fill in

At a glance

Which apps can use it

Related guides

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Discussion

User reviews

Compared with others in Developer toolsi

Common questions

Others in the same category

REA

GitHub

Serena MCP: the IDE for your agent

README from the maker

git-mcp

Features

Quick Start

npx (no install)

Install globally

Claude Desktop

VS Code (Copilot)

Configuration

Tool Reference

Context (git_context)

Status (git_status)

History (git_history)

Commits (git_commits)

Branches (git_branches)

Remotes (git_remotes)

Workspace (git_workspace)

Git Flow (git_flow)

Context (`git_context`)

Status (`git_status`)

History (`git_history`)

Commits (`git_commits`)

Branches (`git_branches`)

Remotes (`git_remotes`)

Workspace (`git_workspace`)

Git Flow (`git_flow`)