Ext Ops Panel
Open dashboard
Comparison

Omi vs Memex — Local AI Memory

Omi is an MCP server published by BasedHardware. Marketplaces we read that list it: 1 (Docker MCP Catalog). Memex — Local AI Memory is a plugin bundle for AI coding tools published by Shvmvrshny. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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
MarketplaceOmiMemex — Local AI Memory
Docker MCP Catalog Listed
Version: sha256:674097f43757
Forks (GitHub): 2 602
Pulls (Docker Hub): 33 749
Stars (Docker Hub): 1
Stars (GitHub): 13 700
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
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

Omi vs Memex — Local AI Memory
FactOmiMemex — Local AI Memory
Marketplaces that list it11
Stars (GitHub) (differs)13 700 (better)2 (worse)
Pulls (Docker Hub) (differs)33 749No figure on Docker Hub
Forks (GitHub) (differs)2 602 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/omi)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)6Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)Not published4
Parts of the bundle (differs)Not a bundle5
LicenceMITMIT
Repository (differs)github.com/basedhardware/omigithub.com/shvmvrshny/memex
Changes in the last 7 days00
First seen2026-10-112026-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.

Memex — Local AI Memory

In its own words, on Claude Code: claude-plugins-community:

Local AI memory system for Claude Code and Cursor. Remembers your preferences, decisions, and project context across sessions using a Go HTTP service and Qdrant vector database running locally in Docker. All data stays on your machine — nothing is sent to the cloud.

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)

Memex — Local AI Memory

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Memex — Local AI Memory publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Memex — Local AI Memory publish no settings it asks for, so we do not compare settings.

What it can do: Omi · What it can do: Memex — Local AI Memory · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built