context-memory vs Builderforce Memory
context-memory is a plugin bundle for AI coding tools published by ErebusEnigma. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Builderforce Memory is an MCP server published by SeanHogg. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
| Marketplace |  Builderforce Memory | |
|---|---|---|
| Community marketplace ccplugins/awesome-claude-code-plugins | Listed Version: 1.3.1 Forks (GitHub): 700 Stars (GitHub): 972 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2026.9.33 Downloads/month (npm): 1 640 Downloads/week (npm): 124 Forks (GitHub): 0 Stars (GitHub): 3 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
| Fact | context-memory | Builderforce Memory |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 972 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 700 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@seanhogg/builderforce-memory-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Hooks it runs (differs) | Not published | 4 |
| Parts of the bundle (differs) | 2 | 6 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/ccplugins/awesome-claude-code-plugins | github.com/seanhogg/builderforce-memory |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-15 | 2026-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
context-memory
Persistent, searchable context storage across Claude Code sessions using SQLite + FTS5.
Builderforce Memory
Token-saving persistent memory for AI agents: recall durable facts instead of re-reading files.
How to run each
context-memory As a Claude Code plugin
/plugin marketplace add ccplugins/awesome-claude-code-plugins
/plugin install context-memory@awesome-claude-code-pluginsBuilderforce Memory As a local MCP server: npm package
claude mcp add --env "BUILDERFORCE_API_KEY=<YOUR_BUILDERFORCE_API_KEY>" --transport stdio builderforce-memory -- npx -y @seanhogg/builderforce-memory-mcpRequires: BUILDERFORCE_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
The marketplaces of context-memory publish no settings it asks for, so we do not compare settings.
What it can do: context-memory · What it can do: Builderforce Memory · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.