Ext Ops Panel
Open dashboard
Comparison

mergify vs io.github.cocaxcode/devflow-mcp

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). io.github.cocaxcode/devflow-mcp is an MCP server published by cocaxcode. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacemergifyio.github.cocaxcode/devflow-mcp
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: 0.1.8
Downloads/month (npm): 263
Downloads/week (npm): 57
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

mergify vs io.github.cocaxcode/devflow-mcp
Factmergifyio.github.cocaxcode/devflow-mcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)32 (better)1 (worse)
Forks (GitHub) (differs)11 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@cocaxcode/devflow-mcp)
Transport (differs)Not statedstdio
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-cligithub.com/cocaxcode/devflow-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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.

io.github.cocaxcode/devflow-mcp

In its own words, on Official MCP Registry:

MCP server connecting Jira (Cloud + Server) with GitHub/GitLab. Branches, issues, PRs, flows.

How to run each

mergify As a Claude Code plugin

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

io.github.cocaxcode/devflow-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio devflow-mcp -- npx -y @cocaxcode/devflow-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: io.github.cocaxcode/devflow-mcp · 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