M
mayank1307/gitferry
v0.4.2 is released.
updated 2026-11-04
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · mayank1307/gitferry · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
mayank1307/gitferry;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# gitferry
Excerpted from the repository README (abridged)
v0.4.2 is released. npm package · v0.4.2 release and downloads · MCP Registry
Portable git-change bundles for air-gapped repos. Pack your unpushed commits, staged/unstaged changes, and untracked files into a single shareable file on one machine — carry it across the air gap (USB, secure file transfer, email, or QR codes across a webcam) — validate and apply it to the same repo on another machine. No shared remote, no network, no sync required.
machine A (has your changes) machine B (same repo, no sync)
┌─────────────────────────┐ ┌─────────────────────────┐
│ $ gitferry pack │ ──────▶ │ $ gitferry apply │
│ → repo-main-a1b2c3d │ USB / │ ✓ checksums verified │
│ .gitferry │ scp / │ ✓ same repo confirmed │
│ │ email │ ✓ 2 commits replayed │
│ commits + worktree │ │ ✓ staged/unstaged │
│ + untracked, checksummed│ │ state restored │
└─────────────────────────┘ └─────────────────────────┘
See SCENARIOS.md for every situation this is built for — air-gapped environments, client-site work, WIP handoffs, offline review, and more. See INSTALL.md for offline installation on other devices.
Quick MCP install (Claude Code): claude mcp add --transport stdio gitferry -- npx --yes --package=gitferry@0.4.2 gitferry-mcp, then restart your client and confirm the pack_changes, inspect_bundle, and apply_bundle tools appear. Codex, VS Code, JSON config, and offline setup are in MCP server below.
## Why not just git format-patch / git bundle?
You can — gitferry uses them under the hood. What raw git doesn't give you:
Untracked files travel too (respecting .gitignore) — git diff never sees them
Staged vs unstaged state is preserved — your index looks the same on the other side
Validation before anything touches the repo: sha256 checksums of every file, same-repository fingerprint check (root commits), base-commit check, clean-tree check
One command each way instead of a multi-step format-patch/diff/am/apply choreography
Binary-safe (--binary patches for tracked files, verbatim bytes for untracked)
Plain-git fallback: the bundle is a zip of standard git patches — pack with --portable and a machine with only git + unzip applies it by hand (instructions are inside every bundle; the compact default needs node's one-liner to unwrap first)
## Install
Requires Node.js 22 or newer and Git 2.32 or newer. Install the published CLI and MCP server from npm:
bash
npm install -g gitferry@0.4.2
gitferry --version
For MCP-only use, skip the global install and use the pinned npx configuration in MCP server.
Installation and MCP registration are separate steps. Installing the npm package makes gitferry and gitferry-mcp available in your terminal. Registering the server tells Codex, Claude Code, or another MCP client how to launch it. With npx, the client downloads the pinned package on first launch, so a global install is optional. Reading this README or installing the package alone does not register the server.
### Closed environments (no npm)
Download gitferry.cjs, gitferry-mcp.cjs, and SHA256SUMS from the public v0.4.2 release. These standalone files include their JavaScript dependencies; transfer them to the offline machine with Node and Git. See INSTALL.md for checksum verification and setup.
Portable git-change bundles for air-gapped repos. Pack your unpushed commits, staged/unstaged changes, and untracked files into a single shareable file on one machine — carry it across the air gap (USB, secure file transfer, email, or QR codes across a webcam) — validate and apply it to the same repo on another machine. No shared remote, no network, no sync required.
machine A (has your changes) machine B (same repo, no sync)
┌─────────────────────────┐ ┌─────────────────────────┐
│ $ gitferry pack │ ──────▶ │ $ gitferry apply │
│ → repo-main-a1b2c3d │ USB / │ ✓ checksums verified │
│ .gitferry │ scp / │ ✓ same repo confirmed │
│ │ email │ ✓ 2 commits replayed │
│ commits + worktree │ │ ✓ staged/unstaged │
│ + untracked, checksummed│ │ state restored │
└─────────────────────────┘ └─────────────────────────┘
See SCENARIOS.md for every situation this is built for — air-gapped environments, client-site work, WIP handoffs, offline review, and more. See INSTALL.md for offline installation on other devices.
Quick MCP install (Claude Code): claude mcp add --transport stdio gitferry -- npx --yes --package=gitferry@0.4.2 gitferry-mcp, then restart your client and confirm the pack_changes, inspect_bundle, and apply_bundle tools appear. Codex, VS Code, JSON config, and offline setup are in MCP server below.
## Why not just git format-patch / git bundle?
You can — gitferry uses them under the hood. What raw git doesn't give you:
Untracked files travel too (respecting .gitignore) — git diff never sees them
Staged vs unstaged state is preserved — your index looks the same on the other side
Validation before anything touches the repo: sha256 checksums of every file, same-repository fingerprint check (root commits), base-commit check, clean-tree check
One command each way instead of a multi-step format-patch/diff/am/apply choreography
Binary-safe (--binary patches for tracked files, verbatim bytes for untracked)
Plain-git fallback: the bundle is a zip of standard git patches — pack with --portable and a machine with only git + unzip applies it by hand (instructions are inside every bundle; the compact default needs node's one-liner to unwrap first)
## Install
Requires Node.js 22 or newer and Git 2.32 or newer. Install the published CLI and MCP server from npm:
bash
npm install -g gitferry@0.4.2
gitferry --version
For MCP-only use, skip the global install and use the pinned npx configuration in MCP server.
Installation and MCP registration are separate steps. Installing the npm package makes gitferry and gitferry-mcp available in your terminal. Registering the server tells Codex, Claude Code, or another MCP client how to launch it. With npx, the client downloads the pinned package on first launch, so a global install is optional. Reading this README or installing the package alone does not register the server.
### Closed environments (no npm)
Download gitferry.cjs, gitferry-mcp.cjs, and SHA256SUMS from the public v0.4.2 release. These standalone files include their JavaScript dependencies; transfer them to the offline machine with Node and Git. See INSTALL.md for checksum verification and setup.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/mayank1307-gitferry/)
- Source
- awesome · https://github.com/mayank1307/gitferry
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.