Ext Ops Panel
Open dashboard
Comparison

breezeware-dev-plugins vs OneTool MCP

breezeware-dev-plugins is a plugin bundle for AI coding tools published by Breezeware-OS. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). OneTool MCP is an MCP server published by beycom. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacebreezeware-dev-pluginsOneTool MCP
Claude Code: claude-plugins-community Listed
Version: 44c96c2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.2.2
Forks (GitHub): 7
Stars (GitHub): 24
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

breezeware-dev-plugins vs OneTool MCP
Factbreezeware-dev-pluginsOneTool MCP
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)24 (better)
Forks (GitHub) (differs)0 (worse)7 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleNot stated
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/breezeware-os/breezeware-claude-pluginsgithub.com/beycom/onetool-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

breezeware-dev-plugins

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

True Claude Code plugins for Breezeware development — auto-detecting, hook-powered, with skills and code review.

OneTool MCP

In its own words, on Official MCP Registry:

One MCP for devs incl Brave,Google,Tavily,Context7,AWS,Excalidraw,DB,GitHub,DevTools,Playwright

How to run each

breezeware-dev-plugins As a Claude Code plugin

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

OneTool MCP

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

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: breezeware-dev-plugins · What it can do: OneTool MCP · 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