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.
We read the source, 23 h ago · rules ccca72095570
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 }),
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.
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.
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.
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.
claude mcp add builderforce-memory -- npx -y @seanhogg/builderforce-memory-mcp
{
"mcpServers": {
"builderforce-memory": {
"args": [
"-y",
"@seanhogg/builderforce-memory-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.builderforce-memory]
command = "npx"
args = ["-y", "@seanhogg/builderforce-memory-mcp"]
{
"mcpServers": {
"builderforce-memory": {
"args": [
"-y",
"@seanhogg/builderforce-memory-mcp"
],
"command": "npx"
}
}
}
{
"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.
Persistent memory for AI agents — 98%+ retrieval recall, 99% token savings, 44 tools
Persistent memory for AI agents — 55 MCP tools, spreading activation recall.
Persistent project memory for AI coding agents: one compact digest instead of re-reading the repo.
Persistent, read-only codebase memory for Claude Code; ask it instead of re-reading files.
Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically.
Memory for AI agents: persistent L1/L2/L3, web-search savings, thread memory.
Persistent memory for AI agents. Store what matters, recall by meaning, skip the rest.
Persistent memory for AI agents. Search and store durable facts, preferences and decisions.
Answers built from our own checks of this server.