Ext Ops Panel
Open dashboard
Comparison

ember-memory vs Echo Memory

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). Echo Memory is an MCP server published by ayushcodes10. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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-memoryEcho Memory
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.5.3
Downloads/month (PyPI): 1 312
Downloads/week (PyPI): 212
Forks (GitHub): 2
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

ember-memory vs Echo Memory
Factember-memoryEcho Memory
Marketplaces that list it11
Stars (GitHub)22
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.echo-mem.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 03, 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/echo-mem/echo-mem
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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.

Echo Memory

In its own words, on Official MCP Registry:

Shared memory for AI agents, as a graph in your own Postgres. Writes never call an LLM.

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

Echo Memory As a remote MCP server

Claude Code
claude mcp add --transport http echo-mem https://api.echo-mem.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: ECHO_MEMORY_AGENT_ID, ECHO_MEMORY_DATABASE_URL (secret), ECHO_MEMORY_USER_ID, Authorization header

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

Only Echo Memory has a remote endpoint we check. How we check endpoints

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 Echo Memory asks for

  • ECHO_MEMORY_AGENT_ID
  • ECHO_MEMORY_DATABASE_URL (secret)
  • ECHO_MEMORY_USER_ID

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

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