Ext Ops Panel
Open dashboard
Comparison

ember-memory vs io.github.omega-memory/core

ember-memory is a plugin bundle for AI coding tools published by KindledFlameStudios. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.omega-memory/core is an MCP server published by omega-memory. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplaceember-memoryio.github.omega-memory/core
Claude Code: claude-plugins-community Listed
Version: 2.0.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.9.3
Forks (GitHub): 32
Stars (GitHub): 222
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

ember-memory vs io.github.omega-memory/core
Factember-memoryio.github.omega-memory/core
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)222 (better)
Forks (GitHub) (differs)0 (worse)32 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (omega-memory)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/kindledflamestudios/ember-memorygithub.com/omega-memory/core
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

ember-memory

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

Persistent semantic memory for Claude Code. Stores knowledge in a local ChromaDB vector database and automatically retrieves relevant context on every message using Ollama bge-m3 embeddings. Everything runs locally — no API keys, no cloud, no data leaving your machine.

io.github.omega-memory/core

In its own words, on Official MCP Registry:

Persistent memory for AI coding agents. #1 on LongMemEval. Local-first.

How to run each

ember-memory

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

io.github.omega-memory/core As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio core -- uvx omega-memory

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.omega-memory/core publish no settings it asks for, so we do not compare settings.

What it can do: ember-memory · What it can do: io.github.omega-memory/core · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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 . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built