SAIHM-Admin/saihm-mcp

**The standards client for your own custodial SAIHM operator.** It carries no
cryptography of its own and expects an operator endpoint URL plus an operator
token. If you just want memory working, free, in about a minute, use
**@saihm/mcp-server-pro** and ask your agent to *"Join SAIHM"*.
· Apache-2.0
**New to SAIHM?** Watch the 6-minute overview (captions and transcript), or read the SAIHM manual (PDF).
This package is the **standards client**: eight memory tools any MCP agent —
Claude Code, Claude Desktop, Cursor, or your own — can call. It carries **no
cryptography of its own**. It speaks the publicly documented SAIHM memory
protocol over plain MCP and reaches whichever SAIHM operator you point it at.
**Which package do I want?**
- **You run, or subscribe to, your own SAIHM operator** — this one. Being
crypto-free and dependency-light is the point: it drops into a **custodial**
operator that performs the cryptography server-side.
→ Install · Configure
- **You just want memory working, free, in about a minute** — use
**@saihm/mcp-server-pro**
and ask your agent to *"Join SAIHM"*. It seals cells on your own machine, so it
can use the hosted **non-custodial** service — which this crypto-free package
cannot. No card. → Free trial
**Want to watch it work first?** Runnable demos across every major model,
offline, no account — **See it run**.
What this is
A Model Context Protocol server
that exposes eight tools any MCP-capable AI agent (Claude Code, Claude Desktop,
custom agents) can call to gain a persistent, encrypted memory layer the
**user** owns:
- saihm_remember — store an encrypted memory cell
- saihm_recall — retrieve your memories, decrypted by your operator
- saihm_forget — erase a memory; whether erasure is cryptographic or access-control depends on your operator (see its documentation)
- saihm_status — your protocol-runtime stats and storage tier dashboard
- saihm_share / saihm_revoke_share — share chosen memory shards, by shard id, with another agent, and revoke that access
- saihm_governance_propose / saihm_governance_vote — protocol governance; **not enabled by default**, so expect an error unless your operator has turned it on
Each tool forwards to a SAIHM operator endpoint that runs the full protocol
stack. The server itself holds no crypto, no storage, and
no protocol runtime — those live behind the operator endpoint.
Tool reference
| Tool | Title | Behavior |
|---|---|---|
| saihm_remember | Remember | writes a new memory cell |
| saihm_recall | Recall | read-only; safe to repeat |
| saihm_forget | Forget (GDPR erasure) | **destructive** — irreversible erasure |
| saihm_status | Status | read-only |
| saihm_share | Share | writes a sharing contract |
| saihm_revoke_share | Revoke share | withdraws a grant |
| saihm_governance_propose | Propose (governance) | forwards a proposal; **not enabled by default** |
| saihm_governance_vote | Vote (governance) | forwards a vote; **not enabled by default** |
Each tool carries MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and a human-readable title, so MCP hosts can gate confirmations and agents can select the right tool at reasoning time.
Companion package
This package speaks MCP and holds no cryptography, so it always needs an
operator endpoint and token. Two companions cover the rest:
- **@saihm/mcp-server-pro**
— a drop-in MCP server that performs the client-side cryptography itself and
can **self-onboard**, including the free tier. This is the package to use if
you have no endpoint yet — see Free trial.
- **@saihm/client-pro** —
the same client-side cryptography as a library, for embedding in your own
application: post-quantum sealing, authenticated sharing, and provable
erasure performed on your own machine so the operator stays blind.
See it run
Runnable, one-command demos ground a memory you own in every major model — Claude, GPT, DeepSeek, Qwen, Kimi, GLM — then prove you can erase it, alongside drop-in adapters for LangChain, LlamaIndex, CrewAI, AutoGen, and LangGraph. Each runs offline in about a minute; no account needed.
- **Live demos:**
- **demo-claude-code** wires this server into Claude Code and Cursor as an MCP server.
**Measured — up to ~86% fewer context tokens.** Most agents re-send their entire transcript every turn, so context spend grows ~O(N²) over a session; recalling a bounded set of memory cells instead cut input tokens by **62.8%–85.9%** across a realistic multi-session coding task. The benchmark is open, offline, and deterministic — reproduce the number rather than trust it: