loveliness vs Neo4j GDS Agent
loveliness is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
loveliness is a plugin bundle for AI coding tools published by Dreamware. No marketplace we read lists it any more. 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. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Neo4j GDS Agent | |
|---|---|---|
| Community marketplace dreamware-nz/loveliness | Removed on 2026-10-26 Version: 0.1.0 Forks (GitHub): 2 Stars (GitHub): 10 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 | lovelinessno longer listed · | Neo4j GDS Agent |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 10 | 98 |
| Forks (GitHub) (differs) | 2 | 23 |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (gds-agent) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 9, secrets among them: 3 |
| Parts of the bundle (differs) | 2 | 3 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/dreamware-nz/loveliness | github.com/neo4j-contrib/gds-agent |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of loveliness
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Official MCP server for Neo4j. Interact with Neo4j using Cypher graph queries.
-
Graph database queries with Cypher and Gremlin.
-
mcp-neo4j-cypher io.github.neo4j-contrib/mcp-neo4j-cypher
A simple Neo4j MCP server that allows you to run Cypher queries against a Neo4j database.
-
mcp-neo4j-data-modeling io.github.neo4j-contrib/mcp-neo4j-data-modeling
A simple Neo4j MCP server for creating graph data models.
-
Knowledge graph hybride — Neo4j + Qdrant + LangGraph. Fournit le MCP graph-server (store/retrieve/relate).
-
Deploy production REST and Neo4j Graph APIs from JSON schemas in seconds.
What each says it does
loveliness
MCP server + skill for the Loveliness clustered graph database (Cypher, bulk load, schema, cluster status)
Neo4j GDS Agent
Neo4j Graph Data Science MCP server
How to run each
loveliness
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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-agentRequires: 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
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of loveliness publish no settings it asks for, so we do not compare settings.
What it can do: loveliness · What it can do: Neo4j GDS Agent · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.