Ext Ops Panel
Open dashboard
Comparison

Neo4j vs alloydb

Neo4j is an MCP server published by neo4j. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). 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

Where each is published
MarketplaceNeo4jalloydb
Docker MCP Catalog Listed
Version: sha256:f22b5fb65f2d
Forks (GitHub): 58
Pulls (Docker Hub): 64 850
Stars (Docker Hub): 0
Stars (GitHub): 299
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 0.2.0
Forks (GitHub): 6
Stars (GitHub): 24
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.0
Forks (GitHub): 6
Stars (GitHub): 24
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

Neo4j vs alloydb
FactNeo4jalloydb
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)299 (better)42 (worse)
Pulls (Docker Hub) (differs)64 850No figure on Docker Hub
Forks (GitHub) (differs)58 (better)7 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/neo4j)On your machine (@toolbox-sdk/server)
Transport (differs)stdioNot stated
Tools it declares (differs)4Not published
Environment variables it asks for (differs)6, secrets among them: 18, secrets among them: 1
Parts of the bundle (differs)Not a bundle8
Licence (differs)NOASSERTIONApache-2.0
Repository (differs)github.com/neo4j/mcpgithub.com/gemini-cli-extensions/alloydb
Changes in the last 7 days (differs)07
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

Neo4j

In its own words, on Docker MCP Catalog:

Official MCP server for Neo4j. Interact with Neo4j using Cypher graph queries.

alloydb

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

Create, connect, and interact with an AlloyDB for PostgreSQL database and data.

How to run each

Neo4j As a local MCP server: Docker image

Claude Code
claude mcp add --env "NEO4J_PASSWORD=<YOUR_NEO4J_PASSWORD>" --transport stdio neo4j -- docker run -i --rm -e NEO4J_PASSWORD mcp/neo4j

Requires: NEO4J_PASSWORD (secret)

alloydb As a Claude Code plugin

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

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 publish no list of tools, so we do not compare tools.

Settings each asks for

Only Neo4j asks for

  • NEO4J_DATABASE
  • NEO4J_PASSWORD (secret)
  • NEO4J_READ_ONLY
  • NEO4J_TELEMETRY
  • NEO4J_URI
  • NEO4J_USERNAME

Only alloydb asks for

  • ALLOYDB_POSTGRES_CLUSTER
  • ALLOYDB_POSTGRES_DATABASE
  • ALLOYDB_POSTGRES_INSTANCE
  • ALLOYDB_POSTGRES_IP_TYPE
  • ALLOYDB_POSTGRES_PASSWORD (secret)
  • ALLOYDB_POSTGRES_PROJECT
  • ALLOYDB_POSTGRES_REGION
  • ALLOYDB_POSTGRES_USER
  • CLOUD_SQL_MSSQL_DATABASE
  • CLOUD_SQL_MSSQL_INSTANCE
  • CLOUD_SQL_MSSQL_IP_TYPE
  • CLOUD_SQL_MSSQL_PASSWORD (secret)
Show the remaining 31
  • CLOUD_SQL_MSSQL_PROJECT
  • CLOUD_SQL_MSSQL_REGION
  • CLOUD_SQL_MSSQL_USER
  • CLOUD_SQL_MYSQL_DATABASE
  • CLOUD_SQL_MYSQL_INSTANCE
  • CLOUD_SQL_MYSQL_IP_TYPE
  • CLOUD_SQL_MYSQL_PASSWORD (secret)
  • CLOUD_SQL_MYSQL_PROJECT
  • CLOUD_SQL_MYSQL_REGION
  • CLOUD_SQL_MYSQL_USER
  • CLOUD_SQL_POSTGRES_DATABASE
  • CLOUD_SQL_POSTGRES_INSTANCE
  • CLOUD_SQL_POSTGRES_IP_TYPE
  • CLOUD_SQL_POSTGRES_PASSWORD (secret)
  • CLOUD_SQL_POSTGRES_PROJECT
  • CLOUD_SQL_POSTGRES_REGION
  • CLOUD_SQL_POSTGRES_USER
  • DATAPLEX_PROJECT
  • DATAPROC_PROJECT
  • DATAPROC_REGION
  • FIRESTORE_DATABASE
  • FIRESTORE_PROJECT
  • ORACLE_CONNECTION_STRING
  • ORACLE_PASSWORD (secret)
  • ORACLE_USERNAME
  • ORACLE_USE_OCI
  • ORACLE_WALLET
  • SPANNER_DATABASE
  • SPANNER_DIALECT
  • SPANNER_INSTANCE
  • SPANNER_PROJECT

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

What it can do: Neo4j · What it can do: alloydb · 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.

Where the data comes from: how the catalog is built