# @seanhogg/builderforce-memory-mcp

BuilderForce Agent Memory — MCP transport. Exposes @seanhogg/builderforce-memory to any MCP client (Claude Agent SDK in-process, stdio, or HTTP) over a pluggable MemoryBackend, with token-saving fetch-on-demand recall.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 2026.9.33
- **Author:** Sean Hogg
- **License:** MIT
- **npm:** @seanhogg/builderforce-memory-mcp
- **Source:** https://github.com/SeanHogg/builderforce-memory
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 7 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-29T12:04:56.644Z
- **Version scanned:** 2026.9.32
- **CVEs:** none found by OSV at scan time

## Tools

8 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `token_usage` — Current token spend + budget for the workspace (today).
- `model_efficiency` — Which models performed best/cheapest for this workspace's recent work.
- `memory_recall` — Semantically recall the most relevant stored memories for a query.
- `memory_get` — Fetch a single memory by its exact key. Use when you already know the key
- `memory_recall_by_tag` — List memories carrying a given tag (e.g. 'user', 'project', 'decision').
- `memory_remember` — Persist a fact for future sessions. Call when you learn something durable and reusable:
- `memory_compact` — Shrink memories that have already been absorbed elsewhere (folded into a model,
- `memory_forget` — Delete a memory by key. Use to remove a fact that is now wrong or obsolete.

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"builderforce-memory\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@seanhogg/builderforce-memory-mcp\"\n      ],\n      \"env\": {\n        \"BUILDERFORCE_API_KEY\": \"<YOUR_BUILDERFORCE_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `BUILDERFORCE_API_KEY` — Builderforce API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40seanhogg%2Fbuilderforce-memory-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40seanhogg%2Fbuilderforce-memory-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40seanhogg%2Fbuilderforce-memory-mcp
- HTML page: https://forgeregistry.com/registry/%40seanhogg%2Fbuilderforce-memory-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.