Community tool: read-only local browser for MemPalace drawers

[henderlabs]

Hi MemPalace maintainers and community,

I built an unofficial companion tool called MemPalace Browser by HenderLabs:

https://github.com/henderlabs/mempalace-browser

It is a small local, read-only browser for inspecting a user's own MemPalace drawers by wing and room. The goal is the human view of the same data that MemPalace already makes available to agents.

I saw the existing Apricity discussion. MemPalace Browser is intentionally much narrower and read-only, so I opened a separate thread to keep the scope and support boundaries clear.

What it does:

• browse wings, rooms, and drawers
• read drawer content and metadata
• run client-side text search
• show local storage information for local backends
• run in demo mode with synthetic drawers, no real palace required

Project boundaries:

• read-only: no add, edit, delete, or re-file endpoints
• imports the installed mempalace package; does not shell out to the CLI
• opens collections with create=False
• does not read chroma.sqlite3 directly
• standard library only, no build step, no runtime dependencies of its own

Security posture:

• binds to 127.0.0.1 by default
• rejects unknown Host headers to reduce DNS-rebinding risk
• no telemetry or analytics
• optional PyPI version check is documented and disableable with MPB_CHECK_UPDATES=0
• demo mode does not import MemPalace or read a palace

This is not a request to merge the tool into core. My ask is smaller: if maintainers think this belongs in the ecosystem, would you accept a docs-only PR that mentions it as an unofficial community companion/browser? If there is a preferred place, wording, or disclaimer, I will follow that.

I am new to public contributions and want to be careful about scope, attribution, and support boundaries.

Thanks,
Phil