Ext Ops Panel
Open dashboard
Comparison

mergify vs GitHub Repo Change Intelligence

mergify is a plugin bundle for AI coding tools published by mergifyio. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). GitHub Repo Change Intelligence is an MCP server published by contentforge-press. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplacemergifyGitHub Repo Change Intelligence
Claude Code: claude-plugins-official Listed
Version: e7c1ebb
Forks (GitHub): 11
Stars (GitHub): 32
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: c862465
Forks (GitHub): 11
Stars (GitHub): 32
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
No figure published
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

mergify vs GitHub Repo Change Intelligence
FactmergifyGitHub Repo Change Intelligence
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)32No figure on GitHub
Forks (GitHub) (differs)11No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (s-github.pixharvest.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)6Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/mergifyio/mergify-cliNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

mergify

In its own words, on Claude Code: claude-plugins-official:

Skills for the Mergify CLI: manage merge queues, stacked pull requests, Test Insights (flaky tests, quarantine), merge protections, and Mergify configuration directly from the terminal.

GitHub Repo Change Intelligence

In its own words, on Official MCP Registry:

Track public GitHub repos: free snapshot, paid release, star & issue intel via x402 USDC.

How to run each

mergify As a Claude Code plugin

Claude Code
/plugin install mergify@claude-plugins-official

GitHub Repo Change Intelligence As a remote MCP server

Claude Code
claude mcp add --transport http github-intel https://s-github.pixharvest.com/mcp

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

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: mergify · What it can do: GitHub Repo Change Intelligence · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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