Amazon Neptune vs Neo4j GDS Agent
Amazon Neptune is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Neo4j GDS Agent is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:aaf8bad96551 Forks (GitHub): 1 835 Pulls (Docker Hub): 12 437 Stars (Docker Hub): 0 Stars (GitHub): 9 839 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 Downloads/month (PyPI): 184 Downloads/week (PyPI): 77 Forks (GitHub): 23 Stars (GitHub): 98 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 | Amazon Neptune | Neo4j GDS Agent |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 9 839 (better) | 98 (worse) |
| Pulls (Docker Hub) (differs) | 12 437 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 835 (better) | 23 (worse) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | On your machine (mcp/amazon-neptune-mcp-server) | On your machine (gds-agent) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 9, secrets among them: 3 |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/neo4j-contrib/gds-agent |
| Changes in the last 7 days | 0 | 0 |
| 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
Amazon Neptune
Graph database queries with Cypher and Gremlin.
Neo4j GDS Agent
Neo4j Graph Data Science MCP server
How to run each
Amazon Neptune As a local MCP server: Docker image
claude mcp add --transport stdio amazon-neptune -- docker run -i --rm mcp/amazon-neptune-mcp-server
Neo4j GDS Agent As a local MCP server: PyPI package
claude mcp add --env "AURA_API_CLIENT_SECRET=<YOUR_AURA_API_CLIENT_SECRET>" --env "NEO4J_PASSWORD=<YOUR_NEO4J_PASSWORD>" --env "NEO4J_URI=<YOUR_NEO4J_URI>" --env "NEO4J_USERNAME=<YOUR_NEO4J_USERNAME>" --transport stdio gds-agent -- uvx gds-agent
Requires: AURA_API_CLIENT_SECRET (secret), 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 Neo4j GDS Agent publish no list of tools, so we do not compare tools.
Settings each asks for
Only Amazon Neptune asks for
AWS_PROFILEAWS_REGIONNEPTUNE_ENDPOINT
Only Neo4j GDS Agent asks for
AURA_API_CLIENT_IDAURA_API_CLIENT_SECRET (secret)AURA_API_PROJECT_IDNEO4J_DATABASENEO4J_PASSWORD (secret)NEO4J_READ_ONLYNEO4J_RESPONSE_TOKEN_LIMIT (secret)NEO4J_URINEO4J_USERNAME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Amazon Neptune · What it can do: Neo4j GDS Agent · 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. 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.