Ext Ops Panel
Open dashboard
Comparison

alloydb vs Claude DB

alloydb is a plugin bundle for AI coding tools published by gemini-cli-extensions. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). Claude DB is a plugin bundle for AI coding tools published by Enrique Rocha. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-23. 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
MarketplacealloydbClaude DB
Claude Code: claude-plugins-official Listed
Version: 0.2.0
Forks (GitHub): 6
Stars (GitHub): 24
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 6
Stars (GitHub): 24
Not marked · First seen
Not listed
Community marketplace hainrixz/claude-db Not listed Listed
Version: 0.1.0
Forks (GitHub): 6
Stars (GitHub): 21
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

alloydb vs Claude DB
FactalloydbClaude DB
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)96 (better)21 (worse)
Forks (GitHub) (differs)13 (better)6 (worse)
Last release (differs)2026-10-16Not published
Where it runs (differs)On your machine (@toolbox-sdk/server)Installs as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)9, secrets among them: 1Not published
Hooks it runs (differs)Not published3
Parts of the bundle (differs)843
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/gemini-cli-extensions/alloydbgithub.com/hainrixz/claude-db
Changes in the last 7 days (differs)20 or more2
First seen (differs)2026-10-112026-10-20

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

alloydb

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

Create, connect, and interact with an AlloyDB for PostgreSQL database and data.

Claude DB

In its own words, on Community GitHub marketplaces:

Design a new database, audit an existing one on two independent axes, and plan safe migrations — across SQL, document, key-value, vector, time-series, and graph engines.

How to run each

alloydb As a Claude Code plugin

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

Claude DB As a Claude Code plugin

Claude Code
/plugin marketplace add hainrixz/claude-db
/plugin install claude-db@claude-db

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 Claude DB publish no settings it asks for, so we do not compare settings.

What it can do: alloydb · What it can do: Claude DB · 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 public marketplace files in GitHub repositories of their authors. 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