Ext Ops Panel
Open dashboard
Comparison

ember-memory vs Make0 Brain

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). Make0 Brain is an MCP server published by make0-official. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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-memoryMake0 Brain
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.3.2
Forks (GitHub): 0
Stars (GitHub): 7
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 Make0 Brain
Factember-memoryMake0 Brain
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)7 (better)
Forks (GitHub)00
Last release (differs)Not published2026-11-07
Where it runs (differs)Installs as a plugin bundleOn your machine (@make0-ai/brain)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 02, secrets among them: 1
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/make0-official/brain-oss
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-28

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.

Make0 Brain

In its own words, on Official MCP Registry:

One shared, versioned memory for Claude Code, Cursor, Codex and every MCP agent. Local and offline.

How to run each

ember-memory As a Claude Code plugin

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

Make0 Brain As a local MCP server: npm package

Claude Code
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio brain-oss -- npx -y @make0-ai/brain

Requires: OPENAI_API_KEY (secret)

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

Only ember-memory asks for

  • EMBER_AI_ID

Only Make0 Brain asks for

  • MAKE0_BRAIN_HOME
  • OPENAI_API_KEY (secret)

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

What it can do: ember-memory · What it can do: Make0 Brain · 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