Ext Ops Panel
Open dashboard
Comparison

quarkus-agent vs CLEO MCP Server

quarkus-agent is a plugin bundle for AI coding tools published by quarkusio. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). CLEO MCP Server is an MCP server published by kryptobaseddev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplacequarkus-agentCLEO MCP Server
Claude Code: claude-plugins-official Listed
Version: 1.2.11
Forks (GitHub): 19
Stars (GitHub): 54
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 1.2.4
Forks (GitHub): 19
Stars (GitHub): 54
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2026.3.35
Downloads/month (npm): 11 934
Downloads/week (npm): 3 797
Forks (GitHub): 24
Stars (GitHub): 159
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

quarkus-agent vs CLEO MCP Server
Factquarkus-agentCLEO MCP Server
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)54 (worse)159 (better)
Forks (GitHub) (differs)19 (worse)24 (better)
Last release (differs)2026-10-16Not published
Where it runs (differs)Installs as a plugin bundleOn your machine (@cleocode/cleo)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/quarkusio/quarkus-agent-mcpgithub.com/kryptobaseddev/cleo
Changes in the last 7 days (differs)20
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

quarkus-agent

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

MCP server for AI coding agents to create, manage, and interact with Quarkus applications. Provides tools for project scaffolding, dev mode lifecycle, extension skills, Dev MCP proxy, and documentation search.

CLEO MCP Server

In its own words, on Official MCP Registry:

Task management for AI coding agents — CQRS 2-gateway pattern, 200 ops across 10 domains

How to run each

quarkus-agent As a Claude Code plugin

Claude Code
/plugin install quarkus-agent@claude-plugins-official

CLEO MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio cleo-mcp-server -- npx -y @cleocode/cleo --mcp-server

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

The marketplaces of quarkus-agent publish no settings it asks for, so we do not compare settings.

What it can do: quarkus-agent · What it can do: CLEO MCP Server · 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