git_archive
Create a git archive (zip or tar).
LABSCO SUMMARY
Read any repository by URL, or drive the one you have checked out.
The clone-and-read half is the unusual part: hand it a URL and it fetches the repository into a deterministic temporary directory, reuses that on the next question, and lets you walk the tree, read files and search code without cloning anything yourself. The rest is a full Git surface including the destructive end — reset, clean and rebase are all here — so your local credentials are the boundary.
What it is
A Git server with two halves. It clones a repository by URL to inspect its tree, files, history and diffs, and it operates on a working copy — branches, commits, staging, push and pull, stash, tags, rebase, reset and revert.
What you get
- A repository's directory tree as an ASCII outline, and the contents of the files you name
- Code searched by pattern across a repository, with file filters, case sensitivity and context lines
- Commit history filtered by author, date range or message, and full commits with their diffs
- Two branches compared, with the changed files and optionally the patch
- Branches created, checked out, merged and deleted
- Files staged and committed, uncommitted changes read back, and work stashed or restored
- Push and pull against a remote, tags created, and archives produced as zip or tar
- Blame, clean, reset, revert and rebase
- Hooks, attributes, repository configuration, and Git LFS objects managed
Requirements
Git installed on the machine and Node to run the server. No account and no key — it operates with whatever access your local Git credentials already have. Cloned repositories land in a temporary directory keyed by the URL and are reused on later calls.
Setup effort
One command — npm install -g git-commands-mcp
USE CASES
01
Reading a repository you have not cloned
Hand over the URL, get the directory tree back, and read the specific files you care about.
02
Finding where something is used
Search the repository for a pattern and get the matching lines with the surrounding context.
03
Working out what changed between branches
Compare the two branches for the file list and commit count, then pull the full commits with their diffs.
04
Seeing what you have not committed yet
Read the working directory's status and diffs before deciding what to stage.
05
Committing a piece of work
Stage the files, commit with a message, and push to the remote in sequence.
06
Setting a change aside
Stash the work in progress, switch to what is urgent, and restore it afterwards.
07
Finding who last touched a line
Read the blame for the file rather than paging through history.
27 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
git_attributes
Manage git attributes for files.
git_blame
Get blame information for a file.
git_branch_diff
Compare two branches and show files changed between them.
git_checkout_branch
Create and/or checkout a branch.
git_clean
Perform git clean operations.
git_commit
Create a commit with the specified message.
git_commit_history
Get commit history for a branch with optional filtering.
git_commits_details
Get detailed information about commits including full messages and diffs.
git_config
Configure git settings for the repository.
git_create_tag
Create a tag.
git_delete_branch
Delete a branch from the repository.
git_directory_structure
Clone a Git repository and return its directory structure in a tree format.
git_hooks
Manage git hooks in the repository.
git_lfs
Manage Git LFS (Large File Storage).
git_lfs_fetch
Fetch LFS objects from the remote repository.
git_local_changes
Get uncommitted changes in the working directory.
git_merge_branch
Merge a source branch into the current or target branch.
git_pull
Pull changes from a remote repository.
git_push
Push changes to a remote repository.
git_read_files
Read the contents of specified files in a given git repository.
git_rebase
Rebase the current branch onto another branch or commit.
git_reset
Reset repository to specified commit or state.
git_revert
Revert the current branch to a commit or state.
git_search_code
Search for patterns in repository code.
git_stash
Create or apply a stash.
git_track
Track (stage) specific files or all files.
BEFORE YOU INSTALL
What to know first
Tools you get
27 tools when we connected. Only seven read-only browsing tools are documented; the undocumented twenty include git_commit, git_push, git_reset, git_clean and git_delete_branch, so a connected agent can change your repository.
Requires
- npx on PATH
- Node.js 14.x or higher
- Git installed on the system
CONTEXT COST
Light Standing cost
Rated by the size of the 27 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"git-commands-mcp": {
"command": "npx",
"args": [
"-y",
"git-commands-mcp"
]
}
}
}npm
TERMINAL
npm install -g git-commands-mcp
