Ext Ops Panel
Open dashboard
Comparison

Meminisse vs Builderforce Memory

Meminisse is a plugin bundle for AI coding tools published by Doğu Abaris. 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: 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
MarketplaceMeminisseBuilderforce Memory
Community marketplace doguabaris/meminisse Listed
Version: 0.5.3
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2026.9.34
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

Meminisse vs Builderforce Memory
FactMeminisseBuilderforce Memory
Marketplaces that list it11
Stars (GitHub) (differs)7 (better)3 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-17
Where it runs (differs)Installs as a plugin bundleOn your machine (@seanhogg/builderforce-memory-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceMITMIT
Repository (differs)github.com/doguabaris/meminissegithub.com/seanhogg/builderforce-memory
Changes in the last 7 days (differs)25
First seen (differs)2026-10-162026-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

Meminisse

In its own words, on Community GitHub marketplaces:

Always-on persistent global and workspace memory for Codex sessions.

Builderforce Memory

In its own words, on Official MCP Registry:

Token-saving persistent memory for AI agents: recall durable facts instead of re-reading files.

How to run each

Meminisse As a Codex plugin

Codex
codex plugin marketplace add doguabaris/meminisse

Builderforce Memory As a local MCP server: npm package

Claude Code
claude mcp add --env "BUILDERFORCE_API_KEY=<YOUR_BUILDERFORCE_API_KEY>" --transport stdio builderforce-memory -- npx -y @seanhogg/builderforce-memory-mcp

Requires: 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 Meminisse publish no settings it asks for, so we do not compare settings.

What it can do: Meminisse · 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.

Where the data comes from: how the catalog is built