alloydb vs Cloudinary Structured Metadata
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). Cloudinary Structured Metadata is an MCP server published by cloudinary.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  Cloudinary Structured Metadata |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 0.2.0 Forks (GitHub): 6 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 0.2.0 Forks (GitHub): 6 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.2 Forks (GitHub): 0 Stars (GitHub): 0 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 | Cloudinary Structured Metadata |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 95 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 13 (better) | 0 (worse) |
| Last release (differs) | 2026-11-04 | Not published |
| Where it runs (differs) | On your machine (@toolbox-sdk/server) | Remote server (structured-metadata.mcp.cloudinary.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 | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/gemini-cli-extensions/alloydb | github.com/cloudinary/structured-metadata-mcp |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 h ago |
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.
Cloudinary Structured Metadata
Create and manage Cloudinary structured metadata fields, datasources, and rules.
How to run each
alloydb As a Claude Code plugin
/plugin install alloydb@claude-plugins-officialCloudinary Structured Metadata As a remote MCP server
claude mcp add --transport http structured-metadata-mcp https://structured-metadata.mcp.cloudinary.com/mcp --header "cloudinary-api-secret: <YOUR_CLOUDINARY_API_SECRET>"Requires: CLOUDINARY_API_KEY, CLOUDINARY_API_SECRET (secret), CLOUDINARY_CLOUD_NAME, cloudinary-api-secret header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Cloudinary Structured Metadata has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only alloydb asks for
ALLOYDB_POSTGRES_CLUSTERALLOYDB_POSTGRES_DATABASEALLOYDB_POSTGRES_INSTANCEALLOYDB_POSTGRES_IP_TYPEALLOYDB_POSTGRES_PASSWORD (secret)ALLOYDB_POSTGRES_PROJECTALLOYDB_POSTGRES_REGIONALLOYDB_POSTGRES_USERCLOUD_SQL_MSSQL_DATABASECLOUD_SQL_MSSQL_INSTANCECLOUD_SQL_MSSQL_IP_TYPECLOUD_SQL_MSSQL_PASSWORD (secret)
Show the remaining 37
CLOUD_SQL_MSSQL_PROJECTCLOUD_SQL_MSSQL_REGIONCLOUD_SQL_MSSQL_USERCLOUD_SQL_MYSQL_DATABASECLOUD_SQL_MYSQL_INSTANCECLOUD_SQL_MYSQL_IP_TYPECLOUD_SQL_MYSQL_PASSWORD (secret)CLOUD_SQL_MYSQL_PROJECTCLOUD_SQL_MYSQL_REGIONCLOUD_SQL_MYSQL_USERCLOUD_SQL_POSTGRES_DATABASECLOUD_SQL_POSTGRES_INSTANCECLOUD_SQL_POSTGRES_IP_TYPECLOUD_SQL_POSTGRES_PASSWORD (secret)CLOUD_SQL_POSTGRES_PROJECTCLOUD_SQL_POSTGRES_REGIONCLOUD_SQL_POSTGRES_USERDATAPLEX_PROJECTDATAPROC_PROJECTDATAPROC_REGIONFIRESTORE_DATABASEFIRESTORE_PROJECTORACLE_CONNECTION_STRINGORACLE_PASSWORD (secret)ORACLE_USERNAMEORACLE_USE_OCIORACLE_WALLETPOSTGRES_DATABASEPOSTGRES_HOSTPOSTGRES_PASSWORD (secret)POSTGRES_PORTPOSTGRES_QUERY_PARAMSPOSTGRES_USERSPANNER_DATABASESPANNER_DIALECTSPANNER_INSTANCESPANNER_PROJECT
Only Cloudinary Structured Metadata asks for
CLOUDINARY_API_KEYCLOUDINARY_API_SECRET (secret)CLOUDINARY_CLOUD_NAME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: alloydb · What it can do: Cloudinary Structured Metadata · 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.