Neo4j Cloud Aura Api vs Infrawise
Neo4j Cloud Aura Api is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 1 (Docker MCP Catalog). Infrawise is an MCP server published by Sidd27. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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 |  Infrawise |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c3db64e4e2bc Forks (GitHub): 263 Pulls (Docker Hub): 16 298 Stars (Docker Hub): 2 Stars (GitHub): 988 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.28.4 Downloads/month (npm): 1 271 Downloads/week (npm): 373 Forks (GitHub): 5 Stars (GitHub): 22 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 | Infrawise |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 988 (better) | 22 (worse) |
| Pulls (Docker Hub) (differs) | 16 298 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 263 (better) | 5 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/neo4j-cloud-aura-api) | On your machine (infrawise) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/neo4j-contrib/mcp-neo4j | github.com/sidd27/infrawise |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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.
Infrawise
Live AWS, database & Kafka infrastructure context for AI coding assistants via MCP.
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)
Infrawise As a local MCP server: npm package
claude mcp add --transport stdio infrawise -- npx -y infrawiseCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Infrawise publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Infrawise publish no settings it asks for, so we do not compare settings.
What it can do: Neo4j Cloud Aura Api · What it can do: Infrawise · 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.