Ext Ops Panel
Open dashboard
Comparison

Omi vs pearl-llm-memory

Omi is an MCP server published by BasedHardware. Marketplaces we read that list it: 1 (Docker MCP Catalog). pearl-llm-memory is a plugin bundle for AI coding tools published by reneemgagnon. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-21. 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
MarketplaceOmipearl-llm-memory
Docker MCP Catalog Listed
Version: sha256:674097f43757
Forks (GitHub): 2 644
Pulls (Docker Hub): 33 893
Stars (Docker Hub): 1
Stars (GitHub): 13 784
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: fff8a3e
No figure published
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 pearl-llm-memory
FactOmipearl-llm-memory
Marketplaces that list it11
Stars (GitHub) (differs)13 784No figure on GitHub
Pulls (Docker Hub) (differs)33 893No figure on Docker Hub
Forks (GitHub) (differs)2 644No figure on GitHub
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
Licence (differs)MITNot stated
Repository (differs)github.com/basedhardware/omigithub.com/reneemgagnon/pearl_llm_memory
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.

pearl-llm-memory

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

Externalized Cognitive State Transfer PEARL-LLM Memory (.pearl) is a JSON-based file format for storing structured, layered, verifiable context that persists across agent sessions. It gives autonomous agents a durable memory with immutable history, temperature-graded recall, cryptographic chain of custody, and branching decision trails. The format is agent-agnostic. The reference implementation is a zero-dependency Python CLI. Both are open.

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)

pearl-llm-memory As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install pearl-llm-memory@claude-community

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

Tools each declares

The marketplaces of pearl-llm-memory publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of pearl-llm-memory publish no settings it asks for, so we do not compare settings.

What it can do: Omi · What it can do: pearl-llm-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