Comparison

Omi vs io.github.neo4j-contrib/mcp-neo4j-memory

Omi is an MCP server published by BasedHardware. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-11-10. 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

Where each is published
Marketplace	Omi	io.github.neo4j-contrib/mcp-neo4j-memory
Docker MCP Catalog	Listed Version: sha256:674097f43757 Forks (GitHub): 2 698 Pulls (Docker Hub): 34 312 Stars (Docker Hub): 1 Stars (GitHub): 13 937 Not marked · First seen 2026-10-11	Listed Version: sha256:0f04105a1006 Forks (GitHub): 261 Pulls (Docker Hub): 45 293 Stars (Docker Hub): 9 Stars (GitHub): 989 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 1.0.0 Downloads/month (PyPI): 23 826 Downloads/week (PyPI): 4 464 Forks (GitHub): 261 Stars (GitHub): 989 Not marked · First seen 2026-10-11

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

Omi vs io.github.neo4j-contrib/mcp-neo4j-memory
Fact	Omi	io.github.neo4j-contrib/mcp-neo4j-memory
Marketplaces that list it (differs)	1 (worse)	2 (better)
Stars (GitHub) (differs)	13 937 (better)	989 (worse)
Pulls (Docker Hub) (differs)	34 312 (worse)	45 293 (better)
Forks (GitHub) (differs)	2 698 (better)	261 (worse)
Last release	Not published	Not published
Where it runs (differs)	On your machine (mcp/omi)	On your machine (mcp-neo4j-memory)
Transport	stdio	stdio
Tools it declares (differs)	6	9
Environment variables it asks for (differs)	1, secrets among them: 1	10, secrets among them: 1
Licence	MIT	MIT
Repository (differs)	github.com/basedhardware/omi	github.com/neo4j-contrib/mcp-neo4j
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

Omi

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for Omi interaction and automation. This server provides tools to read, search, and manipulate Memories and Conversations.

io.github.neo4j-contrib/mcp-neo4j-memory

In its own words, on Official MCP Registry:

MCP Neo4j Knowledge Graph Memory Server

How to run each

Omi As a local MCP server: Docker image

Claude Code

claude mcp add --env "OMI_API_KEY=<YOUR_OMI_API_KEY>" --transport stdio omi -- docker run -i --rm -e OMI_API_KEY mcp/omi

Requires: OMI_API_KEY (secret)

io.github.neo4j-contrib/mcp-neo4j-memory As a local MCP server: PyPI package

Claude Code

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-memory

Requires: 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

Only Omi declares

create_memory
delete_memory
edit_memory
get_conversation_by_id
get_conversations
get_memories

Only io.github.neo4j-contrib/mcp-neo4j-memory declares

add_observations
create_entities
create_relations
delete_entities
delete_observations
delete_relations
find_memories_by_name
read_graph
search_memories

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Omi asks for

OMI_API_KEY (secret)

Only io.github.neo4j-contrib/mcp-neo4j-memory asks for

NEO4J_DATABASE
NEO4J_MCP_SERVER_ALLOWED_HOSTS
NEO4J_MCP_SERVER_ALLOW_ORIGINS
NEO4J_MCP_SERVER_HOST
NEO4J_MCP_SERVER_PATH
NEO4J_MCP_SERVER_PORT
NEO4J_NAMESPACE
NEO4J_PASSWORD (secret)
NEO4J_TRANSPORT
NEO4J_URI
NEO4J_URL
NEO4J_USERNAME

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Omi · What it can do: io.github.neo4j-contrib/mcp-neo4j-memory · 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 2026-11-10. We publish no contact details for plugin publishers.