How do I install Builderforce Memory?

Install via Claude Code (local): 1. Install Claude Code CLI 2. Copy the command below, replace with real env values, then run in terminal 3. See Environment variables below if listed Example: claude mcp add builderforce-memory -- npx -y @seanhogg/builderforce-memory-mcp

What is Builderforce Memory good for?

Builderforce Memory is a fit for: Code review & GitHub, Design & creative, Cursor essentials. See AgentHub scenario pages for pairings.

Builderforce Memory MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.SeanHogg/builderforce-memory · v2026.9.33

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

View on MCP Registry ↗Repository ↗

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Token-saving persistent memory for AI agents: recall durable facts instead of re-reading files. Builderforce Memory is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

Code review & GitHub Design & creative Cursor essentials

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04

Install Snippets TestedCLI & JSON config syntax verified

Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications

Origin Registry ActiveSourced from official-mcp-registry

Verified ClientsClaude Code、Claude Desktop、Cursor 等

Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Score 90/100

Copy by platform

Choose your platform

Open or create .cursor/mcp.json in your project root
Click Copy config and paste; merge only this mcpServers entry if others exist
Replace <placeholders> in env with real secrets (see Environment variables below)
Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

BUILDERFORCE_MEMORY_FILE

BUILDERFORCE_MEMORY_READONLY

BUILDERFORCE_API_KEY

secret

Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.

Click to copy snippet

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

Setup tutorial

Open the Builderforce Memory page and confirm this MCP Server (source: MCP Registry).
Copy the Cursor, Claude Code, or VS Code snippet.
Merge it into mcpServers and replace env placeholders with real secrets.
Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

Install Claude Code CLI
Copy the command below, replace <placeholders> with real env values, then run in terminal
See Environment variables below if listed

claude mcp add builderforce-memory -- npx -y @seanhogg/builderforce-memory-mcp

Cursor — .cursor/mcp.json (local)

Open or create .cursor/mcp.json in your project root
Click Copy config and paste; merge only this mcpServers entry if others exist
Replace <placeholders> in env with real secrets (see Environment variables below)
Save, then Cmd+Shift+P → Reload Window

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

Install GitHub Copilot in VS Code with MCP support
Open or create .vscode/mcp.json in your project root
Click Copy config and paste; merge only this mcpServers entry if others exist
Replace <placeholders> in env with real secrets
Save and Developer: Reload Window

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
Click Copy config and merge under mcpServers
Replace <placeholders> in env with real secrets
Fully quit and restart Claude Desktop

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
Click Copy config and merge mcpServers
Replace <placeholders> in env with real secrets
Save and reload Trae

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

Cherry Studio → Settings → MCP Servers → Add (STDIO)
Or import JSON: click Copy config and merge mcpServers
Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
Enable the server and check tools load

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

Lingma Settings → MCP → + → STDIO or config file
Click Copy config and merge mcpServers
Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
Confirm connected before using tools in agent chat

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

Edit ~/.codeium/windsurf/mcp_config.json
Click Copy config and merge mcpServers (stdio same as Cursor)
Replace <placeholders> in env, save, refresh Cascade

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

Cline — MCP Servers (local)

Cline panel → Settings → MCP Servers
Click Copy config and merge
Replace <placeholders> in env, then save

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
Or Plugins → MCP Servers → Configure MCP and paste the JSON below
Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
Save, restart WorkBuddy, confirm connector status is green

{
  "mcpServers": {
    "builderforce-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@seanhogg/builderforce-memory-mcp"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for Builderforce Memory

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for Builderforce Memory?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet

# Check binary path in terminal:
which npx
node -v

Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

Builderforce Memory requires environment variables (BUILDERFORCE_MEMORY_FILE、BUILDERFORCE_MEMORY_READONLY、BUILDERFORCE_API_KEY). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet

// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}

Still not connecting? Read the MCP troubleshooting guide →

Tool Mock Playground

Sandbox

Builderforce Memory Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready

fn: builderforce_memoryExecute the core tool interface of Builderforce Memory

Request ArgumentsJSON Schema

{
  "target": "Builderforce Memory",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}

💡Parameters generated dynamically by Agent runtime

Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For

PR review
Changelog generation
Cross-repo issue search

When NOT to Use

Replacing human security audit
Unauthorized repo access

Recommended Workflow Pairing:View Scenario →

Most people compare similar tools or check scenario guides before installing—start here.

Browse more like this Search similar Pick by scenario Prompt playbooks MCP hands-on Reviews & comparisons

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

Preview

HTML

<a href="https://myagenthub.cn/p/io.github.SeanHogg/builderforce-memory" title="Listed on AgentHub: Builderforce Memory" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.SeanHogg/builderforce-memory?lang=en" alt="Listed on AgentHub: Builderforce Memory" height="20" style="border:0"/>
</a>

Markdown (GitHub README)

[![Listed on AgentHub: Builderforce Memory](https://myagenthub.cn/badge/io.github.SeanHogg/builderforce-memory?lang=en)](https://myagenthub.cn/p/io.github.SeanHogg/builderforce-memory)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.SeanHogg/builderforce-memory",
  "type": "mcp-server",
  "version": "2026.9.33",
  "displayName": "Builderforce Memory",
  "description": "Token-saving persistent memory for AI agents: recall durable facts instead of re-reading files.",
  "repository": {
    "url": "https://github.com/SeanHogg/builderforce-memory",
    "source": "github",
    "subfolder": "packages/memory-mcp"
  },
  "homepage": "https://builderforce.ai",
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "@seanhogg/builderforce-memory-mcp",
        "version": "2026.9.33",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "BUILDERFORCE_MEMORY_FILE",
            "description": "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."
          },
          {
            "name": "BUILDERFORCE_MEMORY_READONLY",
            "description": "Set to 1 to expose recall only (disables memory_remember and memory_forget)."
          },
          {
            "name": "BUILDERFORCE_API_KEY",
            "description": "Builderforce tenant API key (bfk_*). When set, additionally exposes the token_usage and model_efficiency cost tools.",
            "isSecret": true
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.SeanHogg/builderforce-memory",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.SeanHogg%2Fbuilderforce-memory/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}