mcpbeat Sign in

Builderforce Memory MCP Server

local only

Builderforce Memory runs on your own machine — the client starts it, so there is no endpoint to ping. 106 installs a week from npm. Last commit 5 Oct 2026.

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

Installs per day peak 439 · avg 58 · -87% w/w
a month agotoday
106
Installs / week
npm · @seanhogg/builderforce-memory-mcp
3
Stars
0 open issues
5 Oct 2026
Last commit
8 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 23 h ago · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

            remove: (id) => fs.rmSync(path.join(episodesDir, id), { recursive: true, force: true }),
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Executes code built at runtime packages/memory/src/workflow/code-eval.ts:75
    new Function(code);
    datasetInfo.innerHTML = ds.info;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add builderforce-memory -- npx -y @seanhogg/builderforce-memory-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "builderforce-memory": {
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.builderforce-memory]
command = "npx"
args = ["-y", "@seanhogg/builderforce-memory-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "builderforce-memory": {
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "builderforce-memory": {
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: BUILDERFORCE_MEMORY_FILE (Absolute path to the JSON snapshot that makes memory survive restarts. Defaults to ~/.builderforce-memory/memory.json, which every MCP host on the machine shares.), BUILDERFORCE_MEMORY_READONLY (Set to 1 to expose recall only (disables memory_remember and memory_forget).), BUILDERFORCE_API_KEY (Builderforce tenant API key (bfk_*). When set, additionally exposes the token_usage and model_efficiency cost tools.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to Builderforce Memory

same job, measured the same way
Context Mem
by jubakitiashvili

Persistent memory for AI agents — 98%+ retrieval recall, 99% token savings, 44 tools

130 installs/wk local only
Neural Memory
by nhadaututtheky

Persistent memory for AI agents — 55 MCP tools, spreading activation recall.

41 installs/wk local only
projectmind
by nodemint-dev

Persistent project memory for AI coding agents: one compact digest instead of re-reading the repo.

66 installs/wk local only
Live Memory
by shofer-dev

Persistent, read-only codebase memory for Claude Code; ask it instead of re-reading files.

56 installs/wk local only
DeepMem
by deepmemteam

Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically.

2 tools answering
Vibo Memory
by vnbochkarev-netizen

Memory for AI agents: persistent L1/L2/L3, web-search savings, thread memory.

38 installs/wk local only
Memento Protocol
by myrakrusemark

Persistent memory for AI agents. Store what matters, recall by meaning, skip the rest.

29 installs/wk local only
MemorySync
by memorysync

Persistent memory for AI agents. Search and store durable facts, preferences and decisions.

answering

Builderforce Memory — questions

Answers built from our own checks of this server.

Why is there no uptime for Builderforce Memory?
Builderforce Memory runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @seanhogg/builderforce-memory-mcp was installed 106 times last week.
How do I connect Builderforce Memory?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @seanhogg/builderforce-memory-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Builderforce Memory?
The npm package @seanhogg/builderforce-memory-mcp was installed 106 times in the last week. Week over week that is -87%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Builderforce Memory open source?
Yes — it is published under the MIT licence, written in TypeScript and 3 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.