Ext Ops Panel
Open dashboard
Comparison

rubixkube vs Queue AIops

rubixkube is a plugin bundle for AI coding tools published by rubixkube-io. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Queue AIops is an MCP server published by AIops-tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplacerubixkubeQueue AIops
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.11.0
Downloads/month (PyPI): 977
Downloads/week (PyPI): 145
Forks (GitHub): 0
Stars (GitHub): 0
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

rubixkube vs Queue AIops
FactrubixkubeQueue AIops
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-15
Where it runs (differs)Remote server (mcp.rubixkube.ai/mcp)On your machine (queue-aiops)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/rubixkube-io/rubixkube-for-aigithub.com/aiops-tools/queue-aiops
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 37 h ago, requires a keyno remote endpoint we check

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

rubixkube

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

Site Reliability Intelligence for modern infrastructure. Investigate incidents, review evidence-backed root cause analyses, and track remediation across Kubernetes, AWS, GCP, Linux VMs, and hybrid platforms.

Queue AIops

In its own words, on Official MCP Registry:

Governed redis + rabbitmq ops: memory/latency/backlog/churn RCA, policies. 28 tools.

How to run each

rubixkube As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install rubixkube@claude-community

Queue AIops As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio queue-aiops -- uvx queue-aiops

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

Only rubixkube 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: rubixkube · What it can do: Queue AIops · Compare two other plugins

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