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.
Description from the maker (original English)
A Git MCP server that doesn't suck
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GIT_REPO_PATH, GIT_ALLOW_NO_VERIFY, GIT_ALLOW_FORCE_PUSH, GIT_ALLOW_FLOW_HOOKS, GIT_SIGNING_KEY, GIT_SIGNING_FORMAT, GIT_AUTO_SIGN_COMMITS, GIT_AUTO_SIGN_TAGSValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@selfagency/git-mcp"
],
"env": {
"GIT_REPO_PATH": "your-value",
"GIT_ALLOW_NO_VERIFY": "your-value",
"GIT_ALLOW_FORCE_PUSH": "your-value",
"GIT_ALLOW_FLOW_HOOKS": "your-value",
"GIT_SIGNING_KEY": "your-value",
"GIT_SIGNING_FORMAT": "your-value",
"GIT_AUTO_SIGN_COMMITS": "your-value",
"GIT_AUTO_SIGN_TAGS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add git --env GIT_REPO_PATH=your-value --env GIT_ALLOW_NO_VERIFY=your-value --env GIT_ALLOW_FORCE_PUSH=your-value --env GIT_ALLOW_FLOW_HOOKS=your-value --env GIT_SIGNING_KEY=your-value --env GIT_SIGNING_FORMAT=your-value --env GIT_AUTO_SIGN_COMMITS=your-value --env GIT_AUTO_SIGN_TAGS=your-value -- npx -y @selfagency/git-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@selfagency/git-mcp"
],
"env": {
"GIT_REPO_PATH": "your-value",
"GIT_ALLOW_NO_VERIFY": "your-value",
"GIT_ALLOW_FORCE_PUSH": "your-value",
"GIT_ALLOW_FLOW_HOOKS": "your-value",
"GIT_SIGNING_KEY": "your-value",
"GIT_SIGNING_FORMAT": "your-value",
"GIT_AUTO_SIGN_COMMITS": "your-value",
"GIT_AUTO_SIGN_TAGS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"git": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@selfagency/git-mcp"
],
"env": {
"GIT_REPO_PATH": "your-value",
"GIT_ALLOW_NO_VERIFY": "your-value",
"GIT_ALLOW_FORCE_PUSH": "your-value",
"GIT_ALLOW_FLOW_HOOKS": "your-value",
"GIT_SIGNING_KEY": "your-value",
"GIT_SIGNING_FORMAT": "your-value",
"GIT_AUTO_SIGN_COMMITS": "your-value",
"GIT_AUTO_SIGN_TAGS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
GIT_REPO_PATH envGIT_ALLOW_NO_VERIFY envGIT_ALLOW_FORCE_PUSH envGIT_ALLOW_FLOW_HOOKS envGIT_SIGNING_FORMAT envGIT_AUTO_SIGN_COMMITS envGIT_AUTO_SIGN_TAGS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 7, 2026
The registry name was verified with the GitHub account selfagency, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 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.
You need to fill in: GIT_SIGNING_KEY
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).
The GitHub repo last changed –, and the latest version (0.4.2) reached the registry 23 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
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.
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.
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.shgit_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 appropriategit_rewrite: reword, squash, rewrite-messages, and backup/restore for safe commit-history rewritinggit_analytics: contributors, churn, activity, summary, and file-stats computed from local git historygit_pr: create/list/merge PRs/MRs on GitHub, GitLab, Forgejo, Gitea, and Bitbucket via provider CLI or REST APIgit_tangled_check / git_entire_check detect Tangled hosting and Entire session/context managementrepo_path per-call or configure a server-level defaultgit_worktree: plain git worktree by path, or branch-addressed worktrees via git flow worktree with path templates and provenance-aware cleanupnpx @selfagency/git-mcp --repo-path /path/to/your/repo
npm install -g @selfagency/git-mcp
git-mcp --repo-path /path/to/your/repo
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"] } } }
Add to .vscode/mcp.json in your project:
{
"servers": { "git": { "command": "npx", "args": ["-y", "@selfagency/git-mcp", "--repo-path", "${workspaceFolder}"] } } }
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 |
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.
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 |
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) |
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) |
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 |
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 |
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 |
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)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