Neo4j Cloud Aura Api vs io.github.upstash/mcp-server
Neo4j Cloud Aura Api is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.upstash/mcp-server is an MCP server published by upstash. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  io.github.upstash/mcp-server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c3db64e4e2bc Forks (GitHub): 263 Pulls (Docker Hub): 16 277 Stars (Docker Hub): 2 Stars (GitHub): 988 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.7 Downloads/month (npm): 9 759 Downloads/week (npm): 1 679 Forks (GitHub): 14 Stars (GitHub): 60 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 | io.github.upstash/mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 988 (better) | 60 (worse) |
| Pulls (Docker Hub) (differs) | 16 277 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 263 (better) | 14 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/neo4j-cloud-aura-api) | On your machine (@upstash/mcp-server) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 1 | 3, secrets among them: 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/neo4j-contrib/mcp-neo4j | github.com/upstash/mcp-server |
| 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
Neo4j Cloud Aura Api
Manage Neo4j Aura database instances through the Neo4j Aura API.
io.github.upstash/mcp-server
Manage Upstash databases and resources through the Upstash Developer API.
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)
io.github.upstash/mcp-server As a local MCP server: npm package
claude mcp add --env "UPSTASH_API_KEY=<YOUR_UPSTASH_API_KEY>" --env "UPSTASH_BOX_API_KEY=<YOUR_UPSTASH_BOX_API_KEY>" --env "UPSTASH_EMAIL=<YOUR_UPSTASH_EMAIL>" --transport stdio io-github-upstash-mcp-server -- npx -y @upstash/mcp-serverRequires: UPSTASH_API_KEY (secret), UPSTASH_BOX_API_KEY (secret), UPSTASH_EMAIL
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.upstash/mcp-server 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 io.github.upstash/mcp-server asks for
UPSTASH_API_KEY (secret)UPSTASH_BOX_API_KEY (secret)UPSTASH_EMAIL
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: io.github.upstash/mcp-server · 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.