Ext Ops Panel
Open dashboard
Comparison

alloydb-omni vs io.github.mongodb-js/mongodb-mcp-server

alloydb-omni is a plugin bundle for AI coding tools published by gemini-cli-extensions. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). io.github.mongodb-js/mongodb-mcp-server is an MCP server published by mongodb-js. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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-omniio.github.mongodb-js/mongodb-mcp-server
Claude Code: claude-plugins-official Listed
Version: 0.2.2
Forks (GitHub): 4
Stars (GitHub): 4
Not marked · First seen
Listed
Version: 1.2.1
Forks (GitHub): 42
Stars (GitHub): 190
Not marked · First seen
Claude Code: claude-plugins-community Listed
Version: 0.2.1
Forks (GitHub): 4
Stars (GitHub): 4
Not marked · First seen
Listed
Version: 1.2.0
Forks (GitHub): 42
Stars (GitHub): 190
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 2.1.0
Downloads/month (npm): 503 570
Downloads/week (npm): 100 749
Forks (GitHub): 312
Stars (GitHub): 1 146
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:6ab64d0ba27f
Forks (GitHub): 312
Pulls (Docker Hub): 156 174
Stars (Docker Hub): 11
Stars (GitHub): 1 146
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 io.github.mongodb-js/mongodb-mcp-server
Factalloydb-omniio.github.mongodb-js/mongodb-mcp-server
Marketplaces that list it (differs)2 (worse)5 (better)
Stars (GitHub) (differs)4 (worse)1 146 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub156 174
Forks (GitHub) (differs)4 (worse)312 (better)
Last release (differs)2026-10-16 (worse)2026-10-16 (better)
Where it runs (differs)On your machine (@toolbox-sdk/server)On your machine (mongodb-mcp-server)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published25
Environment variables it asks for (differs)6, secrets among them: 142, secrets among them: 4
Parts of the bundle99
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/gemini-cli-extensions/alloydb-omnigithub.com/mongodb-js/mongodb-mcp-server
Changes in the last 7 days44
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.

io.github.mongodb-js/mongodb-mcp-server

In its own words, on Official MCP Registry:

MongoDB Model Context Protocol Server

How to run each

alloydb-omni As a Claude Code plugin

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

io.github.mongodb-js/mongodb-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "MDB_MCP_API_CLIENT_ID=<YOUR_MDB_MCP_API_CLIENT_ID>" --env "MDB_MCP_API_CLIENT_SECRET=<YOUR_MDB_MCP_API_CLIENT_SECRET>" --env "MDB_MCP_CONNECTION_STRING=<YOUR_MDB_MCP_CONNECTION_STRING>" --env "MDB_MCP_VOYAGE_API_KEY=<YOUR_MDB_MCP_VOYAGE_API_KEY>" --transport stdio mongodb-mcp-server -- npx -y mongodb-mcp-server

Requires: MDB_MCP_API_CLIENT_ID (secret), MDB_MCP_API_CLIENT_SECRET (secret), MDB_MCP_CONNECTION_STRING (secret), MDB_MCP_VOYAGE_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of alloydb-omni publish no list of tools, so we do not compare tools.

Settings each asks for

Only alloydb-omni asks for

  • ALLOYDB_OMNI_DATABASE
  • ALLOYDB_OMNI_HOST
  • ALLOYDB_OMNI_PASSWORD (secret)
  • ALLOYDB_OMNI_PORT
  • ALLOYDB_OMNI_QUERY_PARAMS
  • ALLOYDB_OMNI_USER

Only io.github.mongodb-js/mongodb-mcp-server asks for

  • MDB_MCP_ALLOW_REQUEST_OVERRIDES
  • MDB_MCP_API_CLIENT_ID (secret)
  • MDB_MCP_API_CLIENT_SECRET (secret)
  • MDB_MCP_ASSISTANT_BASE_URL
  • MDB_MCP_ATLAS_TEMPORARY_DATABASE_USER_LIFETIME_MS
  • MDB_MCP_CONFIRMATION_REQUIRED_TOOLS
  • MDB_MCP_CONNECTION_SCOPE
  • MDB_MCP_CONNECTION_STRING (secret)
  • MDB_MCP_DISABLED_TOOLS
  • MDB_MCP_DISABLE_SERVER_SIDE_JS
  • MDB_MCP_DRY_RUN
  • MDB_MCP_ELICITATION_TIMEOUT_MS
Show the remaining 30
  • MDB_MCP_EXPORTS_PATH
  • MDB_MCP_EXPORT_CLEANUP_INTERVAL_MS
  • MDB_MCP_EXPORT_TIMEOUT_MS
  • MDB_MCP_EXTERNALLY_MANAGED_SESSIONS
  • MDB_MCP_HEALTH_CHECK_HOST
  • MDB_MCP_HEALTH_CHECK_PORT
  • MDB_MCP_HTTP_BODY_LIMIT
  • MDB_MCP_HTTP_HEADERS
  • MDB_MCP_HTTP_HOST
  • MDB_MCP_HTTP_PORT
  • MDB_MCP_HTTP_RESPONSE_TYPE
  • MDB_MCP_IDLE_TIMEOUT_MS
  • MDB_MCP_INDEX_CHECK
  • MDB_MCP_LOGGERS
  • MDB_MCP_LOG_PATH
  • MDB_MCP_MAX_ACTIVE_CONNECTIONS
  • MDB_MCP_MAX_BYTES_PER_QUERY
  • MDB_MCP_MAX_DOCUMENTS_PER_QUERY
  • MDB_MCP_MAX_SESSIONS
  • MDB_MCP_MAX_TIME_M_S
  • MDB_MCP_MCP_CLIENT_LOG_LEVEL
  • MDB_MCP_MONITORING_SERVER_FEATURES
  • MDB_MCP_MONITORING_SERVER_HOST
  • MDB_MCP_MONITORING_SERVER_PORT
  • MDB_MCP_NOTIFICATION_TIMEOUT_MS
  • MDB_MCP_PREVIEW_FEATURES
  • MDB_MCP_READ_ONLY
  • MDB_MCP_TELEMETRY
  • MDB_MCP_TRANSPORT
  • MDB_MCP_VOYAGE_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: alloydb-omni · What it can do: io.github.mongodb-js/mongodb-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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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