Neo4j Cloud Aura Api vs PlanetScale
Neo4j Cloud Aura Api is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 1 (Docker MCP Catalog). PlanetScale is an MCP server published by planetscale. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |  PlanetScale |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c3db64e4e2bc Forks (GitHub): 262 Pulls (Docker Hub): 16 273 Stars (Docker Hub): 2 Stars (GitHub): 988 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 4 Stars (GitHub): 5 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 | PlanetScale |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 988 (better) | 5 (worse) |
| Pulls (Docker Hub) (differs) | 16 273 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 262 (better) | 4 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/neo4j-cloud-aura-api) | Remote server (mcp.pscale.dev/mcp/planetscale) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/neo4j-contrib/mcp-neo4j | github.com/planetscale/mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
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.
PlanetScale
Connect to PlanetScale databases, branches, schema, query insights, and execute SQL
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)
PlanetScale As a remote MCP server
claude mcp add --transport http planetscale https://mcp.pscale.dev/mcp/planetscaleCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PlanetScale has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of PlanetScale publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of PlanetScale publish no settings it asks for, so we do not compare settings.
What it can do: Neo4j Cloud Aura Api · What it can do: PlanetScale · 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.