Builderforce Memory vs io.github.mem0ai/mem0
Builderforce Memory is an MCP server published by SeanHogg. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). io.github.mem0ai/mem0 is an MCP server published by mem0ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 | |
|---|---|---|
| Official MCP Registry | Listed Version: 2026.9.33 Downloads/month (npm): 1 640 Downloads/week (npm): 124 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 1.0.0 No figure published 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 | Builderforce Memory | io.github.mem0ai/mem0 |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@seanhogg/builderforce-memory-mcp) | Remote server (mcp.mem0.ai/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/seanhogg/builderforce-memory | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 307 (2 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
Builderforce Memory
Token-saving persistent memory for AI agents: recall durable facts instead of re-reading files.
io.github.mem0ai/mem0
Persistent memory for AI agents: add, search, update, and delete long-term memories.
How to run each
Builderforce 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)
io.github.mem0ai/mem0 As a remote MCP server
claude mcp add --transport http mem0 https://mcp.mem0.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.mem0ai/mem0 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
The marketplaces of io.github.mem0ai/mem0 publish no settings it asks for, so we do not compare settings.
What it can do: Builderforce Memory · What it can do: io.github.mem0ai/mem0 · 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.