Fluxgit MCP server
io.github.fluxgit-hq/fluxgit-mcp-server·v0.2.1Safety-first Git MCP server: rich read tools plus human-approved FluxGit operation proposals.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Fluxgit yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Fluxgit tools
No tool declarations could be read from the package source. They show once the server is installed.
How Fluxgit compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 1,119 Developer tools servers
Release history: 2 versions in the registry since 2026-09-26, latest 2026-09-28, typically one every 2 days.
Install Fluxgit in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Fluxgit repository's README, as published. We do not edit it. Read it on GitHub
fluxgit-mcp-sidecar
<!-- mcp-name: io.github.fluxgit-hq/fluxgit-mcp-server -->
mcp-name: io.github.fluxgit-hq/fluxgit-mcp-server
Safety-first Model Context Protocol (MCP) server for Git.
AI agents inspect. FluxGit keeps control.
A Rust MCP server with 34 contracts for AI code agents: 23 read-only tools and 11 human-gated operation tools (10 proposals plus cancellation of a pending proposal). The sidecar never executes a Git write; it bridges approved proposals to the FluxGit desktop application.
For context-budget comparisons, see the public Git context token benchmark. It publishes the fixture, raw outputs, scripts and checksums, including both the broad CLI sweep and a smaller hand-tuned counterexample.
Why this exists
AI coding agents are increasingly asked to navigate real repositories: explain branch state, summarize diffs, find lost commits, recommend safe next steps. To do this well, an agent needs Git context that is richer than git status and structured enough to reason over. To do this safely, an agent must never be able to silently mutate refs, force-push, discard work, or apply patches without a human approving the consequence.
Other MCP Git servers face a choice: stay strictly read-only (limited utility) or expose write tools directly (dangerous — agents hallucinate, prompts can be poisoned, mistakes are destructive). This sidecar chooses neither. Inspection is schema-validated and bounded; operations go through a write-with-UI-handshake: the agent proposes, FluxGit shows the preview, the user approves in the app, and FluxGit executes through its safety pipeline with restore points and audit.
What's exposed
23 read-only tools
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Fluxgit: common questions
- Is Fluxgit MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Fluxgit safety report
- Does Fluxgit need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Fluxgit maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v0.2.1.
- What can I use instead of Fluxgit?
- Servers from other publishers that do the same job: Nexusmem MCP server, git-into-gsoc MCP server and Gnt MCP server.
Alternatives to Fluxgit
Same job from other publishers: the closest match first, then the best rated.
- NexusmemLocal-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.not reviewedGrowingA
git-into-gsocEvidence-based GSoC preparation: organizations, repositories, free beginner issues, proposals.not reviewedGrowingA- GntGit-native policy layer for AI agents: check_action verdicts against rules approved via PR.not reviewedGrowingA
- Pare GitPare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON.not reviewedGrowingA
RepowiseCodebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.not reviewedEstablishedB
