Ext Ops Panel
Open dashboard
Comparison

Omi vs iai-pme — personal memory engine

Omi is an MCP server published by BasedHardware. Marketplaces we read that list it: 1 (Docker MCP Catalog). iai-pme — personal memory engine is a plugin bundle for AI coding tools published by Areg Aramovich Noya. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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
MarketplaceOmiiai-pme — personal memory engine
Docker MCP Catalog Listed
Version: sha256:674097f43757
Forks (GitHub): 2 644
Pulls (Docker Hub): 33 894
Stars (Docker Hub): 1
Stars (GitHub): 13 784
Not marked · First seen
Not listed
Community marketplace codeabra/iai-personal-memory-engine Not listed Listed
Version: 3.2.3
Forks (GitHub): 111
Stars (GitHub): 911
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 iai-pme — personal memory engine
FactOmiiai-pme — personal memory engine
Marketplaces that list it11
Stars (GitHub) (differs)13 784 (better)911 (worse)
Pulls (Docker Hub) (differs)33 894No figure on Docker Hub
Forks (GitHub) (differs)2 644 (better)111 (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 bundle4
LicenceMITMIT
Repository (differs)github.com/basedhardware/omigithub.com/codeabra/iai-personal-memory-engine
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15

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.

iai-pme — personal memory engine

In its own words, on Community GitHub marketplaces:

Persistent local memory for your assistant: every turn captured verbatim, relevant memory injected at session start and before each turn, and fourteen memory tools over MCP. Requires the iai-pme package (pip install iai-pme).

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)

iai-pme — personal memory engine As a Claude Code plugin

Claude Code
/plugin marketplace add codeabra/iai-personal-memory-engine
/plugin install iai-memory@iai-pme

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

Tools each declares

The marketplaces of iai-pme — personal memory engine publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of iai-pme — personal memory engine publish no settings it asks for, so we do not compare settings.

What it can do: Omi · What it can do: iai-pme — personal memory engine · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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