alloydb vs Contextflo
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). Contextflo is an MCP server published by contextflo.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
| Marketplace |  alloydb | |
|---|---|---|
| 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 |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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
| Fact | alloydb | Contextflo |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 42 | No figure on GitHub |
| Forks (GitHub) (differs) | 7 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@toolbox-sdk/server) | Remote server (mcp.contextflo.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/gemini-cli-extensions/alloydb | Not stated |
| Changes in the last 7 days (differs) | 7 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Create, connect, and interact with an AlloyDB for PostgreSQL database and data.
Contextflo
Query your warehouse or a CSV with Claude/ChatGPT over MCP, governed by table-level ACL + audit.
How to run each
alloydb As a Claude Code plugin
/plugin install alloydb@claude-plugins-officialContextflo As a remote MCP server
claude mcp add --transport http contextflo https://mcp.contextflo.com/mcpCommands 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 Contextflo publish no settings it asks for, so we do not compare settings.
What it can do: alloydb · What it can do: Contextflo · 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.