joakimp/mempalace-toolkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

pi bridge: RemoteMcpClient is now the only copy (pi-extensions retired mcp-loader.ts)

Browse Source 
pi-extensions 750b2a8 removed mcp-loader.ts in favour of pi's built-in MCP
support (builtin:mcp, ~/.pi/agent/mcp.json). The bridge's RemoteMcpClient was
vendored from that file and kept in step by an MCP-STREAMABLE-HTTP-CLIENT-SYNC
token, checked by scripts/check-mcp-client-sync.sh. With the canonical copy
gone the guard could only ever SKIP (or, on images that still bake
/opt/pi-extensions/extensions/mcp-loader.ts, compare against a dead file), so
it is removed rather than left looking like a check.

Comment and README only; no code change. The bridge still type-strips and
imports (node 24), and evaluateDormancy is exported as before. The README
records why MemPalace itself does not move to the built-in: its wake-up,
mailbox, feed and stamping need their own client, and built-in tools would be
mcp__mempalace__* with codemode exposure by default.
This commit is contained in:
Joakim Persson
2026-10-13 00:17:02 +02:00
parent 975ab92943
commit a30af61883
3 changed files with 17 additions and 92 deletions
Download Patch File Download Diff File Expand all files Collapse all files
extensions/pi/README.md
+9 -5
View File
@@ -211,12 +211,16 @@ chosen at load time:
also pins `Host`/`Origin`, so a request arriving under the wrong hostname is
refused even when the port is open.
Implementation note: the HTTP client (`RemoteMcpClient`) is **vendored** from
Implementation note: the HTTP client (`RemoteMcpClient`) was **vendored** from
[`pi-extensions`](https://gitea.jordbo.se/joakimp/pi-extensions)'
`mcp-loader.ts`. A `MCP-STREAMABLE-HTTP-CLIENT-SYNC` token keeps the two
copies from drifting — [`scripts/check-mcp-client-sync.sh`](../../scripts/check-mcp-client-sync.sh)
fails if they diverge (it skips gracefully when the `pi-extensions` checkout
isn't present).
`mcp-loader.ts`. That loader was retired on 2026-10-12 (pi-extensions
`750b2a8`) in favour of pi's built-in MCP support, so this copy is now the
only one. The sync token and `scripts/check-mcp-client-sync.sh` that guarded
the pair were removed with it. MemPalace itself does **not** move to the
built-in: the bridge's wake-up, mailbox, feed and provenance stamping need
their own client, and built-in MCP tools would be renamed
`mcp__mempalace__*` with `codemode` exposure (not declared to the model) by
default.
## Fail-soft