Align OpenCode with hosted MCP architecture

[ishaanxgupta]

Switches agent-facing memory actions to hosted MCP while keeping automatic recall and capture in hooks. Keeps only the login and status commands, improves diagnostics, and adds a fixed Supermemory footer.

[ishaanxgupta]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Align OpenCode with hosted MCP architecture #82 👈 (View in Graphite)
• Add persistent Supermemory status to OpenCode #81
• Show Supermemory activity in OpenCode #80
• Harden recall and capture reliability #78
• Capture durable human memory #77
• Recall memories directly on substantive prompts #76
• Improve recall result quality #75
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[vorflux]

Cross-checked this migration against the hosted MCP worker in supermemory and the API/self-hosted boundary in mono. I found three material regressions in the new routing path.

---

Review with Vorflux

[vorflux]

Full-stack comparison against the current Claude Code plugin found one additional material MCP registration difference.

---

Review with Vorflux

[vorflux]

P2 — Preserve an existing user-defined mcp.supermemory server. This spreads the MCP map but unconditionally replaces its supermemory entry and forces it enabled. A user who already configured that name for a self-hosted endpoint, custom command/environment, or intentionally disabled server will silently be redirected to this bundled proxy. Claude’s bundled MCP is plugin-namespaced (mcp__plugin_supermemory_supermemory__...) rather than overwriting a user-global entry. Please preserve an existing entry or register the proxy under a collision-resistant plugin-owned key unless the user explicitly opts into replacement.