Ext Ops Panel
Open dashboard
Comparison

atuin-memory vs Builderforce Memory

atuin-memory is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

atuin-memory is a plugin bundle for AI coding tools published by Brian Cosgrove. No marketplace we read lists it any more. 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-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceatuin-memoryBuilderforce Memory
Community marketplace cosgroveb/claude-atuin-memory-skill Removed on 2026-10-18
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2026.10.31
Downloads/month (npm): 3 160
Downloads/week (npm): 1 208
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

atuin-memory vs Builderforce Memory
Factatuin-memoryno longer listed · Builderforce Memory
Marketplaces that list it (differs)01
Stars (GitHub)33
Forks (GitHub)00
Last release (differs)Not published2026-10-28
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
Licence (differs)Not statedMIT
Repository (differs)github.com/cosgroveb/claude-atuin-memory-skillgithub.com/seanhogg/builderforce-memory
Changes in the last 7 days (differs)010
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of atuin-memory

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • origin

    AI work memory for Claude Code: brief, capture, recall, handoff, and distill, backed by a local daemon and MCP so decisions, lessons, project context, and wiki pages carry across…

    by Qi-Xuan Lu · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • claude-memory

    A Claude Code plugin that adds structured, categorized memory to your projects.

    by tars23364-bit · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • pmm

    If you have ever had AI hallucinate and make things up (and gaslight you, even): it's because summaries do not preserve nuance. Each /compact cycle summarises and compresses…

    by NominexHQ · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • origin

    Personal AI memory layer. Capture decisions, lessons, and context that carry across sessions.

    by 7xuanlu · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • Total Agent Memory

    Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall

    by vbcherepanov · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • Remem

    Persistent project memory for Codex through remem MCP and explicit hook activation.

    by majiayu000 · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

atuin-memory

In its own words, on Community GitHub marketplaces:

Persist project roadmap and feature memory in atuin, with optional cross-project priming memory.

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

atuin-memory

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

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

Where the data comes from: how the catalog is built