Ext Ops Panel
Open dashboard
Comparison

alloydb-omni vs StackQL MCP Server

alloydb-omni 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). StackQL MCP Server is an MCP server published by stackql. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacealloydb-omniStackQL MCP Server
Claude Code: claude-plugins-official Listed
Version: 0.2.1
Forks (GitHub): 4
Stars (GitHub): 4
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.2.1
Forks (GitHub): 4
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.12.778
Forks (GitHub): 87
Stars (GitHub): 1 069
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-omni vs StackQL MCP Server
Factalloydb-omniStackQL MCP Server
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)4 (worse)1 069 (better)
Forks (GitHub) (differs)4 (worse)87 (better)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (@toolbox-sdk/server)On your machine (https://github.com/stackql/stackql/releases/download/v0.12.778/stackql-mcp-linux-x64.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)6, secrets among them: 1Not published
Parts of the bundle (differs)9Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/gemini-cli-extensions/alloydb-omnigithub.com/stackql/stackql
Changes in the last 7 days22
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

alloydb-omni

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

Create, connect, and interact with an AlloyDB Omni database and data.

StackQL MCP Server

In its own words, on Official MCP Registry:

SQL-native query and provisioning engine for cloud infrastructure, served over MCP.

How to run each

alloydb-omni As a Claude Code plugin

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

StackQL MCP Server

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

The marketplaces of StackQL MCP Server publish no settings it asks for, so we do not compare settings.

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