mcp-memory-bucket 0.7.4 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -168,6 +168,26 @@ memory/skill sources. Override that with one of:
168
168
  Note the `--` before `--memory-dir` — without it, npm swallows the flag
169
169
  itself instead of passing it through to the script.
170
170
 
171
+ - the `FOLDERFOO_MODE` environment variable, or the `--folderfoo-mode
172
+ <off|dev|cloud>` CLI flag — controls whether the web UI integrates with
173
+ folderfoo (remote skill/memory folders backed by a folderfoo server, plus
174
+ the `folderfoo-profile-circle` login widget). Defaults to `off`: no folderfoo
175
+ code loads, no login widget appears, no network calls to any folderfoo
176
+ server are made. Set to `dev` to point at a local folderfoo dev server
177
+ (`http://localhost:3000`, e.g. via `folderfoo/start-dev.sh`), or `cloud`
178
+ for the real hosted deployment (`https://files.cuul.cc`).
179
+
180
+ ```sh
181
+ npm start -- --folderfoo-mode dev
182
+ # or: FOLDERFOO_MODE=dev npm start
183
+ ```
184
+
185
+ Unlike browser-only folderfoo consumers (mindfoo, bulletino, avotuner),
186
+ which infer dev-vs-prod from `window.location.hostname`, mcp-memory-bucket
187
+ is a CLI tool whose own page is always `localhost` regardless of which
188
+ folderfoo deployment (if any) is wanted — hence the explicit flag instead
189
+ of hostname-sniffing.
190
+
171
191
  ## Test
172
192
 
173
193
  ```sh