Ext Ops Panel
Open dashboard
Comparison

io.github.fluxgit-hq/fluxgit-mcp-server vs GitEasy MCP

io.github.fluxgit-hq/fluxgit-mcp-server is an MCP server published by fluxgit-hq. Marketplaces we read that list it: 1 (Official MCP Registry). GitEasy MCP is an MCP server published by greenmtnsun. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.fluxgit-hq/fluxgit-mcp-serverGitEasy MCP
Official MCP Registry Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.6.2
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.fluxgit-hq/fluxgit-mcp-server vs GitEasy MCP
Factio.github.fluxgit-hq/fluxgit-mcp-serverGitEasy MCP
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-25
Where it runs (differs)On your machine (fluxgit-mcp-sidecar)Remote server (giteasy-mcp.azurewebsites.net/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/fluxgit-hq/fluxgit-mcp-servergithub.com/greenmtnsun/giteasy
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.fluxgit-hq/fluxgit-mcp-server

In its own words, on Official MCP Registry:

Safety-first Git MCP server: rich read tools plus human-approved FluxGit operation proposals.

GitEasy MCP

In its own words, on Official MCP Registry:

Plain-English git for agents: 22 tools to branch, commit, push and tag. Free tier.

How to run each

io.github.fluxgit-hq/fluxgit-mcp-server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

GitEasy MCP As a remote MCP server

Claude Code
claude mcp add --transport http giteasy https://giteasy-mcp.azurewebsites.net/mcp --header "X-Api-Key: <YOUR_X_API_KEY>"

Requires: X-Api-Key header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only GitEasy MCP has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.fluxgit-hq/fluxgit-mcp-server · What it can do: GitEasy MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built