Git MCP server
✓ VerifiedLets an AI client manage local Git repositories including status, logs, diffs, branches, and gated commits using pure JavaScript.
Also known as Abhishekkumar2021/mcp-suite, @abhishekmcp/git, @abhishekmcp/files
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- 389
- Latest version
- 0.2.0
- Last commit
- Jul 4, 2026
- License
- MIT
What is Git MCP?
Git lets an AI client manage local Git repositories including status, logs, diffs, branches, and gated commits using pure JavaScript.
Summary generated from the project's README
About Git MCP server
Managing local version control directly through an AI client is what this server enables for developers. It provides a way to interact with Git repositories using pure JavaScript, meaning it does not require a local git binary to function. This makes it highly portable across different environments when connected to clients like Claude Desktop, Claude Code, or Cursor.
Users can perform a variety of repository management tasks including checking status, viewing logs, inspecting diffs, and managing branches or tags. The server also supports remote operations such as cloning, fetching, pulling, and pushing. To ensure safety during the development process, it includes gated stage and commit tools to prevent accidental changes. It is distributed as an independent npm package, making it easy to integrate into existing workflows via npx or MCPB bundles.
What you can do with it
- 1Inspect repository changesAn AI can examine the current state of a project and view specific code differences.
- 2Manage version control historyDevelopers can ask an AI to review the commit history or list existing branches.
- 3Perform remote repository operationsThe client can handle synchronization tasks like pulling updates or pushing new code to a remote.
- 4Execute controlled commitsYou can instruct an AI to stage and commit files using a protected workflow.
Written from the project's README. Every use case is checked against a quote from it.
How to install Git MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Git MCP in Claude Code
$ claude mcp add --env 'GIT_ROOTS=<GIT_ROOTS>' git -- npx -y @abhishekmcp/gitInstall Git MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@abhishekmcp/git"
],
"env": {
"GIT_ROOTS": "<GIT_ROOTS>"
}
}
}
}Install Git MCP in VS Code
.vscode/mcp.json
{
"servers": {
"git": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@abhishekmcp/git"
],
"env": {
"GIT_ROOTS": "<GIT_ROOTS>"
}
}
}
}Install Git MCP in VS Code CLI
$ code --add-mcp '{"name":"git","type":"stdio","command":"npx","args":["-y","@abhishekmcp/git"],"env":{"GIT_ROOTS":"<GIT_ROOTS>"}}'Install Git MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@abhishekmcp/git"
],
"env": {
"GIT_ROOTS": "<GIT_ROOTS>"
}
}
}
}Install Git MCP in Codex
$ codex mcp add git --env 'GIT_ROOTS=<GIT_ROOTS>' -- npx -y @abhishekmcp/gitInstall Git MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.git] command = "npx" args = ["-y", "@abhishekmcp/git"] [mcp_servers.git.env] GIT_ROOTS = "<GIT_ROOTS>"
Install Git MCP in Gemini CLI
$ gemini mcp add -s user -e 'GIT_ROOTS=<GIT_ROOTS>' git npx -- -y @abhishekmcp/gitInstall Git MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@abhishekmcp/git"
],
"env": {
"GIT_ROOTS": "<GIT_ROOTS>"
}
}
}
}Configuration
GIT_ROOTSRequiredAllowed repo root directories (comma-separated). Required — the server refuses to start without it.
GIT_WRITABLESet to 1 or true to enable local write tools (stage/commit/branch/checkout).
NOTES_DIR
| Name | Description | |
|---|---|---|
| GIT_ROOTS | Allowed repo root directories (comma-separated). Required — the server refuses to start without it. | Required |
| GIT_WRITABLE | Set to 1 or true to enable local write tools (stage/commit/branch/checkout). | |
| NOTES_DIR | — |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableabhishekkumar2021/mcp-suite is public and reachablegithub.com/abhishekkumar2021/mcp-suite ↗Pass
- Package names this repository as its source@abhishekmcp/git, @abhishekmcp/files name abhishekkumar2021/mcp-suite as sourcenpmjs.com/package/@abhishekmcp/git ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @abhishekmcp/git, @abhishekmcp/filesnpmjs.com/package/@abhishekmcp/git/v/0.2.0#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-07-04github.com/abhishekkumar2021/mcp-suite ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @abhishekmcp/git, @abhishekmcp/filesPass
- No critical advisory in the package or its dependencies130 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub🧰 mcp-suite
A collection of Model Context Protocol servers, built in TypeScript.
Each server lives in its own folder under servers/ and publishes to npm as an independent package, while sharing tooling through an npm workspace. Connect them to any MCP client — Claude Desktop, Claude Code, Cursor, and more.
Table of contents
- Servers
- Quickstart
- Install
- Connecting to a client
- Architecture & conventions
- Development
- Adding a new server
- Publishing
- Contributing
- License
Servers
| Server | Description | Status |
|---|---|---|
notes |
Local markdown notes: ranked full-text and semantic search, tags, todos, a [[wiki-link]] knowledge graph, daily notes + templates, and slash-command workflows (prompts) |
✅ Stable |
files |
Sandboxed local filesystem: read, glob + content search, token-efficient edits, copy/move, soft-delete trash, zip, checksums, and dedup | ✅ Stable |
github |
GitHub: search repos/code/issues, read repos/issues/PRs/files, notifications, create issues — OAuth device flow or token | ✅ Stable |
git |
Git: status, log, diff, file history, branches/tags, gated stage/commit, and remote clone/fetch/pull/push — pure-JS, no git binary | ✅ Stable |
sql |
SQL databases: read-only query + schema introspection over Postgres & SQLite, gated writes | ✅ Stable |
http |
HTTP/REST client: ad-hoc requests + saved collections/environments, env secrets, host-allowlisted + SSRF-safe | ✅ Stable |
More on the way: a Spotify controller, and others.
Quickstart
git clone https://github.com/Abhishekkumar2021/mcp-suite.git
cd mcp-suite
npm install # installs deps for every workspace
npm run build # builds every server
Install
Every server ships through every common channel. For the Claude Code plugin, add the marketplace
once — /plugin marketplace add Abhishekkumar2021/mcp-suite — then install per the table. See each
server's README for full config.
| Server | Claude Code plugin | npm (any client) | Claude Desktop (MCPB) | MCP registry |
|---|---|---|---|---|
notes |
/plugin install notes |
npx -y @abhishekmcp/notes |
drag notes-*.mcpb from the latest release |
io.github.Abhishekkumar2021/notes |
files |
/plugin install files |
npx -y @abhishekmcp/files |
drag files-*.mcpb |
io.github.Abhishekkumar2021/files |
github |
/plugin install github |
npx -y @abhishekmcp/github |
drag github-*.mcpb |
io.github.Abhishekkumar2021/github |
git |
/plugin install git |
npx -y @abhishekmcp/git |
drag git-*.mcpb |
io.github.Abhishekkumar2021/git |
sql |
/plugin install sql |
npx -y @abhishekmcp/sql |
drag sql-*.mcpb |
io.github.Abhishekkumar2021/sql |
http |
/plugin install http |
npx -y @abhishekmcp/http |
drag http-*.mcpb |
io.github.Abhishekkumar2021/http |
notesdefaults to~/notes;filesrequiresFS_ROOTS(the directories it may touch). MCPB bundles install via Claude Desktop → Settings → Extensions.
Connecting to a client
Each server's README has full configuration instructions. As an example, to use the notes server with Claude Code:
claude mcp add notes --env NOTES_DIR=$HOME/notes -- node "$(pwd)/servers/notes/dist/index.js"
Or with Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"notes": {
"command": "node",
"args": ["/absolute/path/to/mcp-suite/servers/notes/dist/index.js"],
"env": { "NOTES_DIR": "/absolute/path/to/your/notes" }
}
}
}
Architecture & conventions
A few principles hold across every server:
- Pure-JS/WASM by default; native only when genuinely required. Servers run via
npx/MCPB on any machine, so portable pure-JS/WebAssembly is strongly preferred and a native dependency is used only when genuinely required (gated + documented). In practice these servers are dependency-light:notesuses MiniSearch + WebAssembly embeddings,sqluses thesql.jsWASM SQLite engine, andfilesusesfast-globinstead of ripgrep.npm auditstays clean. - Sandbox-first, layered design. Each server keeps a thin
index.ts(tool registration only) over focused modules, with a single security boundary every path must pass through (realpath-containment, symlink-escape rejection, atomic writes). - Token-efficient by default. Pagination, head/tail/section reads, snippets, and compact graph refs keep tool output small.
- Automated, hands-off releases. A GitHub Release tagged
<server>-v<version>publishes to npm (with provenance), the official MCP registry, and attaches an MCPB bundle — all via OIDC, no secrets. - Tested in CI. Each server ships a committed
node:testsuite (unit + integration/security) run on every push.
Development
This is an npm workspaces monorepo.
npm install # install all workspace dependencies (run once at the root)
npm run build # build every server
npm run build -w servers/notes # build a single server
npm test --workspaces --if-present # run each server's test suite
npm run clean # remove all build output
Adding a new server
- Create
servers/<name>/with its ownpackage.json(unique npmname) and atsconfig.jsonthatextends: "../../tsconfig.base.json". - Put source in
servers/<name>/src/. - Run
npm installat the root so the workspace picks it up. - Add a row to the Servers table above.
All servers follow the naming standard (@abhishekmcp/<slug>). See CONTRIBUTING.md for detailed guidelines.
Publishing
Releases are automated. Cutting a GitHub Release tagged <server>-v<version> triggers
publish.yml, which — authenticated entirely via GitHub OIDC (no
NPM_TOKEN) — publishes the package to npm with provenance, registers it on the official MCP
registry, and builds + attaches the MCPB bundle to the release.
# bump servers/<name>/package.json, commit, then:
gh release create <name>-v<version> --title "<name> v<version>" --notes "…"
Contributing
Contributions are welcome! Please read CONTRIBUTING.md and our Code of Conduct. Found a security issue? See SECURITY.md.
License
MIT © Abhishek
Git MCP questions
How do I add Git MCP to Claude Code?
Run claude mcp add --env 'GIT_ROOTS=<GIT_ROOTS>' git -- npx -y @abhishekmcp/git in your terminal. Add --scope user to make it available in every project.
How do I add Git MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does this Git server require a local Git binary installed?
No, the server is written in pure JavaScript and does not require a Git binary to function.
What Git operations can the AI perform with this server?
The server supports checking status, viewing logs and diffs, inspecting file history and branches/tags, performing gated staging and commits, and managing remotes via clone, fetch, pull, and push.
How can I install the Git MCP server?
You can install it via npm using npx -y @abhishekmcp/git or by adding the Claude Code plugin.