Ext Ops Panel
Open dashboard
Comparison

repo-actions-hub vs Mooring

repo-actions-hub is a plugin bundle for AI coding tools published by James Montemagno. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Mooring is an MCP server published by seayniclabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplacerepo-actions-hubMooring
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.2
Forks (GitHub): 5 207
Stars (GitHub): 40 365
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Downloads/month (PyPI): 65
Downloads/week (PyPI): 24
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 0 (last published figure)
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

repo-actions-hub vs Mooring
Factrepo-actions-hubMooring
Marketplaces that list it11
Stars (GitHub) (differs)40 3650 (last published figure)
Forks (GitHub) (differs)5 2070 (last published figure)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mooring-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/github/awesome-copilotgithub.com/seayniclabs/mooring
Changes in the last 7 days (differs)10
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

repo-actions-hub

In its own words, on Copilot CLI: github/awesome-copilot:

Browse repository GitHub Actions workflows, inspect recent runs, and trigger manual workflow_dispatch runs from a Copilot canvas.

Mooring

In its own words, on Official MCP Registry:

Git and GitHub operations — repo status, diffs, branches, PRs, issues, and Actions.

How to run each

repo-actions-hub

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

Mooring As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mooring -- uvx mooring-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: repo-actions-hub · What it can do: Mooring · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/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