Circleback vs io.github.neo4j-contrib/mcp-neo4j-memory
Circleback is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). io.github.neo4j-contrib/mcp-neo4j-memory is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-20. 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 |  io.github.neo4j-contrib/mcp-neo4j-memory | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 268 Stars (GitHub): 12 913 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (PyPI): 23 826 Downloads/week (PyPI): 3 565 Forks (GitHub): 263 Stars (GitHub): 989 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:0f04105a1006 Forks (GitHub): 263 Pulls (Docker Hub): 38 030 Stars (Docker Hub): 9 Stars (GitHub): 989 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 | Circleback | io.github.neo4j-contrib/mcp-neo4j-memory |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 12 913 (better) | 989 (worse) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 38 030 |
| Forks (GitHub) (differs) | 1 268 (better) | 263 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (circleback.ai/api/mcp) | On your machine (mcp-neo4j-memory) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 9 |
| Environment variables it asks for (differs) | Not published | 10, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/cursor/plugins | github.com/neo4j-contrib/mcp-neo4j |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | no remote endpoint we check |
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
Circleback
Search meetings, transcripts, action items, and emails.
io.github.neo4j-contrib/mcp-neo4j-memory
MCP Neo4j Knowledge Graph Memory Server
How to run each
Circleback
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.neo4j-contrib/mcp-neo4j-memory As a local MCP server: PyPI package
claude mcp add --env "NEO4J_PASSWORD=<YOUR_NEO4J_PASSWORD>" --env "NEO4J_URI=<YOUR_NEO4J_URI>" --env "NEO4J_USERNAME=<YOUR_NEO4J_USERNAME>" --transport stdio mcp-neo4j-memory -- uvx mcp-neo4j-memoryRequires: 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.
Only Circleback has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Circleback publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Circleback publish no settings it asks for, so we do not compare settings.
What it can do: Circleback · What it can do: io.github.neo4j-contrib/mcp-neo4j-memory · Compare two other plugins
Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.