Ext Ops Panel
Open dashboard
Comparison

memory-bank vs Engram: AI memory you can edit in Obsidian

memory-bank is a plugin bundle for AI coding tools published by cjgl23. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Engram: AI memory you can edit in Obsidian is an MCP server published by engram-app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplacememory-bankEngram: AI memory you can edit in Obsidian
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.54.0
Forks (GitHub): 3
Stars (GitHub): 11
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

memory-bank vs Engram: AI memory you can edit in Obsidian
Factmemory-bankEngram: AI memory you can edit in Obsidian
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)11 (better)
Forks (GitHub) (differs)1 (worse)3 (better)
Last release (differs)Not published2026-10-18
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.engram.page)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/cjgl23/claude-memory-bank-plugingithub.com/engram-app/engram
Changes in the last 7 days (differs)010
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

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

memory-bank

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

memory-bank is a Claude Code plugin that helps maintain project context across sessions by keeping a structured memory-bank/ directory of Markdown files. It is designed to: Initialize a standard set of memory bank docs for a project. Keep context current as work evolves. Remind/block stopping when project files changed but the memory bank has not been updated.

Engram: AI memory you can edit in Obsidian

In its own words, on Official MCP Registry:

Shared memory for Claude, ChatGPT and any MCP client. Read and edit it in Obsidian or the web app.

How to run each

memory-bank As a Claude Code plugin

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

Engram: AI memory you can edit in Obsidian As a remote MCP server

Claude Code
claude mcp add --transport http engram https://mcp.engram.page

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

Only Engram: AI memory you can edit in Obsidian 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

Neither one's marketplaces publish the settings it asks for.

What it can do: memory-bank · What it can do: Engram: AI memory you can edit in Obsidian · 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