Ext Ops Panel
Open dashboard
Comparison

Compartment vs Builderforce Memory

Compartment is an MCP server published by MaxFreedomPollard. Marketplaces we read that list it: 2 (Official MCP Registry, 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-14. 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
MarketplaceCompartmentBuilderforce Memory
Official MCP Registry Listed
Version: 4.11.0
Downloads/month (PyPI): 1 599
Downloads/week (PyPI): 198
Forks (GitHub): 7
Stars (GitHub): 581
Not marked · First seen
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

Compartment vs Builderforce Memory
FactCompartmentBuilderforce Memory
Marketplaces that list it22
Stars (GitHub) (differs)581 (better)3 (worse)
Forks (GitHub) (differs)7 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (compartment)On your machine (@seanhogg/builderforce-memory-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Hooks it runs (differs)Not published4
Parts of the bundle (differs)26
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/maxfreedompollard/compartmentgithub.com/seanhogg/builderforce-memory
Changes in the last 7 days22
First seen2026-10-112026-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

Compartment

In its own words, on Official MCP Registry:

Durable agentic memory, encrypted at rest. Fully offline: no network, no API key, no cloud.

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

Compartment As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio compartment -- uvx compartment serve

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

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

Where the data comes from: how the catalog is built