Ext Ops Panel
Open dashboard
Comparison

Neo4j vs io.github.letoribo/mcp-graphql-enhanced

Neo4j is an MCP server published by neo4j. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.letoribo/mcp-graphql-enhanced is an MCP server published by letoribo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplaceNeo4jio.github.letoribo/mcp-graphql-enhanced
Docker MCP Catalog Listed
Version: sha256:f22b5fb65f2d
Forks (GitHub): 59
Pulls (Docker Hub): 105 499
Stars (Docker Hub): 0
Stars (GitHub): 300
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.15.4
Downloads/month (npm): 92 780
Downloads/week (npm): 31 380
Forks (GitHub): 3
Stars (GitHub): 6
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 io.github.letoribo/mcp-graphql-enhanced
FactNeo4jio.github.letoribo/mcp-graphql-enhanced
Marketplaces that list it11
Stars (GitHub) (differs)300 (better)6 (worse)
Pulls (Docker Hub) (differs)105 499No figure on Docker Hub
Forks (GitHub) (differs)59 (better)3 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/neo4j)On your machine (@letoribo/mcp-graphql-enhanced)
Transportstdiostdio
Tools it declares (differs)4Not published
Environment variables it asks for (differs)6, secrets among them: 17, secrets among them: 0
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/neo4j/mcpgithub.com/letoribo/mcp-graphql-enhanced
Changes in the last 7 days00
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.

io.github.letoribo/mcp-graphql-enhanced

In its own words, on Official MCP Registry:

GraphQL gateway for LLMs. Handles huge GitHub GraphQL & @neo4j/graphql schemas without crashing

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)

io.github.letoribo/mcp-graphql-enhanced As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcp-graphql-enhanced -- npx -y @letoribo/mcp-graphql-enhanced

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

Tools each declares

The marketplaces of io.github.letoribo/mcp-graphql-enhanced 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 io.github.letoribo/mcp-graphql-enhanced asks for

  • ALLOW_MUTATIONS
  • ENABLE_HTTP
  • ENDPOINT
  • HEADERS
  • MCP_PORT
  • NAME
  • SCHEMA

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

What it can do: Neo4j · What it can do: io.github.letoribo/mcp-graphql-enhanced · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built