Ext Ops Panel
Open dashboard
Comparison

alloydb vs io.github.neo4j-contrib/mcp-neo4j-memory

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). io.github.neo4j-contrib/mcp-neo4j-memory is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-27. 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
Marketplacealloydbio.github.neo4j-contrib/mcp-neo4j-memory
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
Downloads/month (PyPI): 23 826
Downloads/week (PyPI): 7 866
Forks (GitHub): 264
Stars (GitHub): 989
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:0f04105a1006
Forks (GitHub): 264
Pulls (Docker Hub): 40 400
Stars (Docker Hub): 9
Stars (GitHub): 989
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 vs io.github.neo4j-contrib/mcp-neo4j-memory
Factalloydbio.github.neo4j-contrib/mcp-neo4j-memory
Marketplaces that list it (differs)3 (better)2 (worse)
Stars (GitHub) (differs)96 (worse)989 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub40 400
Forks (GitHub) (differs)13 (worse)264 (better)
Last release (differs)2026-10-16Not published
Where it runs (differs)On your machine (@toolbox-sdk/server)On your machine (mcp-neo4j-memory)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published9
Environment variables it asks for (differs)8, secrets among them: 110, secrets among them: 1
Parts of the bundle (differs)8Not a bundle
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/gemini-cli-extensions/alloydbgithub.com/neo4j-contrib/mcp-neo4j
Changes in the last 7 days (differs)20 or more0
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

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

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

io.github.neo4j-contrib/mcp-neo4j-memory

In its own words, on Official MCP Registry:

MCP Neo4j Knowledge Graph Memory Server

How to run each

alloydb As a Claude Code plugin

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

io.github.neo4j-contrib/mcp-neo4j-memory As a local MCP server: PyPI package

Claude Code
claude mcp add --env "NEO4J_PASSWORD=<YOUR_NEO4J_PASSWORD>" --env "NEO4J_URI=<YOUR_NEO4J_URI>" --env "NEO4J_USERNAME=<YOUR_NEO4J_USERNAME>" --transport stdio mcp-neo4j-memory -- uvx mcp-neo4j-memory

Requires: NEO4J_PASSWORD (secret), NEO4J_URI, NEO4J_USERNAME

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 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 47
  • 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
  • MSSQL_DATABASE
  • MSSQL_HOST
  • MSSQL_PASSWORD (secret)
  • MSSQL_PORT
  • MSSQL_USER
  • MYSQL_DATABASE
  • MYSQL_HOST
  • MYSQL_PASSWORD (secret)
  • MYSQL_PORT
  • MYSQL_USER
  • ORACLE_CONNECTION_STRING
  • ORACLE_PASSWORD (secret)
  • ORACLE_USERNAME
  • ORACLE_USE_OCI
  • ORACLE_WALLET
  • POSTGRES_DATABASE
  • POSTGRES_HOST
  • POSTGRES_PASSWORD (secret)
  • POSTGRES_PORT
  • POSTGRES_QUERY_PARAMS
  • POSTGRES_USER
  • SPANNER_DATABASE
  • SPANNER_DIALECT
  • SPANNER_INSTANCE
  • SPANNER_PROJECT

Only io.github.neo4j-contrib/mcp-neo4j-memory asks for

  • NEO4J_DATABASE
  • NEO4J_MCP_SERVER_ALLOWED_HOSTS
  • NEO4J_MCP_SERVER_ALLOW_ORIGINS
  • NEO4J_MCP_SERVER_HOST
  • NEO4J_MCP_SERVER_PATH
  • NEO4J_MCP_SERVER_PORT
  • NEO4J_NAMESPACE
  • NEO4J_PASSWORD (secret)
  • NEO4J_TRANSPORT
  • NEO4J_URI
  • NEO4J_URL
  • NEO4J_USERNAME

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

What it can do: alloydb · What it can do: io.github.neo4j-contrib/mcp-neo4j-memory · 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