io.github.0Mattias/bettermemory vs Builderforce Memory
io.github.0Mattias/bettermemory is an MCP server published by 0Mattias. Marketplaces we read that list it: 1 (Official MCP Registry). Builderforce Memory is an MCP server published by SeanHogg. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  io.github.0Mattias/bettermemory |  Builderforce Memory |
|---|---|---|
| Official MCP Registry | Listed Version: 8.0.0 Downloads/month (PyPI): 4 973 Downloads/week (PyPI): 702 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2026.10.3 Downloads/month (npm): 1 640 Downloads/week (npm): 80 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 | io.github.0Mattias/bettermemory | Builderforce Memory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 3 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | On your machine (bettermemory) | On your machine (@seanhogg/builderforce-memory-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/0mattias/bettermemory | github.com/seanhogg/builderforce-memory |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen | 2026-10-11 | 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
io.github.0Mattias/bettermemory
Memory for coding agents, checked against the filesystem and git before it is believed.
Builderforce Memory
Token-saving persistent memory for AI agents: recall durable facts instead of re-reading files.
How to run each
io.github.0Mattias/bettermemory As a local MCP server: PyPI package
claude mcp add --transport stdio bettermemory -- uvx bettermemoryBuilderforce 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 io.github.0Mattias/bettermemory publish no settings it asks for, so we do not compare settings.
What it can do: io.github.0Mattias/bettermemory · What it can do: Builderforce Memory · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.