Neo4j Cloud Aura Api vs alloydb-omni
Neo4j Cloud Aura Api is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). As of our marketplace pass on 2026-10-17. 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 |  Neo4j Cloud Aura Api |  alloydb-omni |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c3db64e4e2bc Forks (GitHub): 262 Pulls (Docker Hub): 16 276 Stars (Docker Hub): 2 Stars (GitHub): 988 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 0.2.2 Forks (GitHub): 4 Stars (GitHub): 4 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.2.1 Forks (GitHub): 4 Stars (GitHub): 4 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 | Neo4j Cloud Aura Api | alloydb-omni |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 988 (better) | 4 (worse) |
| Pulls (Docker Hub) (differs) | 16 276 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 262 (better) | 4 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/neo4j-cloud-aura-api) | On your machine (@toolbox-sdk/server) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 1 | 6, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 9 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/neo4j-contrib/mcp-neo4j | github.com/gemini-cli-extensions/alloydb-omni |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-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
Neo4j Cloud Aura Api
Manage Neo4j Aura database instances through the Neo4j Aura API.
alloydb-omni
Create, connect, and interact with an AlloyDB Omni database and data.
How to run each
Neo4j Cloud Aura Api As a local MCP server: Docker image
claude mcp add --env "NEO4J_AURA_CLIENT_SECRET=<YOUR_NEO4J_AURA_CLIENT_SECRET>" --transport stdio neo4j-cloud-aura-api -- docker run -i --rm -e NEO4J_AURA_CLIENT_SECRET mcp/neo4j-cloud-aura-apiRequires: NEO4J_AURA_CLIENT_SECRET (secret)
alloydb-omni As a Claude Code plugin
/plugin install alloydb-omni@claude-plugins-officialCommands 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 Neo4j Cloud Aura Api asks for
NEO4J_AURA_CLIENT_IDNEO4J_AURA_CLIENT_SECRET (secret)NEO4J_MCP_SERVER_ALLOWED_HOSTSNEO4J_MCP_SERVER_ALLOW_ORIGINSNEO4J_MCP_SERVER_HOSTNEO4J_MCP_SERVER_PATHNEO4J_MCP_SERVER_PORTNEO4J_TRANSPORT
Only alloydb-omni asks for
ALLOYDB_OMNI_DATABASEALLOYDB_OMNI_HOSTALLOYDB_OMNI_PASSWORD (secret)ALLOYDB_OMNI_PORTALLOYDB_OMNI_QUERY_PARAMSALLOYDB_OMNI_USER
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Neo4j Cloud Aura Api · What it can do: alloydb-omni · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.