Other · Local MCP server
Builderforce Memory
Token-saving persistent memory for AI agents: recall durable facts instead of re-reading files.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.SeanHogg/builderforce-memory- Version
- 2026.9.33
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- SeanHogg (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/SeanHogg) · how
- Website
- builderforce.ai
- Repository
- github.com/SeanHogg/builderforce-memory (folder packages/memory-mcp)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @seanhogg/builderforce-memory-mcp | 2026.9.33 | stdio |
How to connect Builderforce Memory
Builderforce Memory runs locally from a Node.js package published to the npm registry: @seanhogg/builderforce-memory-mcp version 2026.9.33. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @seanhogg/builderforce-memory-mcp@2026.9.33. It reads these environment variables: BUILDERFORCE_MEMORY_FILE, BUILDERFORCE_MEMORY_READONLY and BUILDERFORCE_API_KEY (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"builderforce-memory": {
"command": "npx",
"args": [
"-y",
"@seanhogg/builderforce-memory-mcp@2026.9.33"
],
"env": {
"BUILDERFORCE_MEMORY_FILE": "<value>",
"BUILDERFORCE_MEMORY_READONLY": "<value>",
"BUILDERFORCE_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from SeanHogg (GitHub)
| Server | Runs |
|---|---|
| BuilderforceRun tickets, boards, OKRs and cloud coding agents in your Builderforce workspace. | Remote · HTTPLive check: sign-in required |
More other servers
| Server | Runs |
|---|---|
| BugCatcherBug reports, AI diagnosis, and status management for Cursor, Claude, Windsurf. | Local · stdio |
| BugEzyVoice-powered bug reporting with 13 MCP tools. Record bugs by talking; let AI find and fix them. | Remote · HTTPLive check: ✓ handshake |
| Build Cache MCPSummarize local build and cache footprint using size and age buckets without returning paths or... | Local · stdio |
| build123d MCPAI-driven 3D CAD via build123d: execute, render, measure, and export geometry interactively. | Local · stdio |
| BuilderVet - NSW builder licence & risk historyIs this NSW builder licensed, insolvent or disciplined? 178k+ licences from official registers. | Remote · HTTPLive check: ✓ handshake |
| BuildFlow Enterprise OperationsDiscover, route, and hand off enterprise operations problems without exposing private records. | Remote · HTTPLive check: ✓ handshake |
| BuildiumRead Buildium properties, units, leases, tenants, balances and bills; manage work orders. | Remote · HTTPLive check: ✓ handshake |
| Built with Jon - Hidden Profit ToolsRead-only tools for finding where a small business leaks deals, time, and cash. | Remote · HTTPLive check: ✗ no handshake |