Portable memory for AI agents — enterprise-ready production thin-client. Seals agent memory client-side (ML-DSA-65 / AES-256-GCM / ML-KEM-768) and stores opaque ciphertext on the blind, non-custodial SAIHM /mcp endpoint. Pairs with @saihm/client-pro and @saihm/mcp-server.
claude mcp add saihm-mcp-server-pro -- npx -y saihm-mcp-server-pro
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
1 ★ · SAIHM-Admin/saihm-mcp-server-pro · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 1 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository SAIHM-Admin/saihm-mcp-server-pro;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
**Portable memory for AI agents.** Your assistant remembers what matters — across sessions, across models, across vendors. Share a memory with someone else's agent, take it back, or erase it for good. ▶ SAIHM Short Overview 6 minutes ▶ SAIHM Detailed Overview 30 minutes **Enjoyed them?** Like the videos, subscribe to the SAIHM channel, and turn on notifications with the bell 🔔 to hear about new videos and updates. **Prefer to read?** The SAIHM manual (PDF) is a decision-maker's guide to SAIHM and SHM. AI assistants forget everything when the session ends. SAIHM gives yours a memory that doesn't — one that follows you to a different assistant, a different model, or a different company's product. **Encrypted at rest, by default.** Every memory is encrypted on your own machine before it goes anywhere, and SAIHM stores only that ciphertext. Nobody else can read your memories — not the storage, not SAIHM. There is nothing to switch on. Start free — one command No card and no wallet. You need a browser and a GitHub account once, for a quick sign-in that confirms you're a real person: 1. The command creates your key on this machine and shows a link and a short code. 2. Open the link, sign in to GitHub, enter the code and approve. 3. The command finishes by itself and shows where your key is saved. **No GitHub account?** Start at instead: you sign in with Google, and the page gives you your new key. Save it to a file only you can read, and point SAIHM_MASTER_SECRET_FILE at that file in your client's settings below. Never paste the key itself into a settings file. Your key is ready, so skip *"Join SAIHM"*: a join would make a second, different key. Then add SAIHM to your AI client, restart it, and say **"Recall my SAIHM memories."** You're running. **Prefer not to touch a terminal?** Add SAIHM to your client first, then say **"Join SAIHM"** to your assistant. It runs the same setup and gives you the same link and code to approve. **If a join is interrupted**, join again on the same machine: it reuses the key it already created, so you keep the same identity. To cancel a join, stop it and don't enter the code; the code expires on its own. Keep the key file either way. Joining in detail. Add SAIHM to your AI client The configurations below for Claude Code, Gemini CLI and the OpenAI Agents SDK are presented as tested (which clients are checked); the others are documented from each vendor's own documentation. Every configuration is subject to change at the vendor's discretion. SAIHM runs on your machine as a local MCP server that your AI client starts with npx, so you need Node.js 20 or later. The package is @saihm/mcp-server-pro on npm, and the official MCP Registry lists it as io.github.SAIHM-Admin/saihm-mcp-server-pro. Find your client below, add its block, and restart the client. Three tips: - **Keep the file valid.** A trailing comma, or a non-breaking space copied from an email or a web page, makes a JSON settings file invalid. Paste through a plain-text editor. - **Keep the start-up setting.** The first start downloads the package. Where a block sets a longer start-up time, keep it, so the tools appear on the first try. - **Download it once first.** Run npx -y @saihm/mcp-server-pro --version in a terminal. It downloads the package, prints its version and exits, so the client's first start is quick. Each block follows that client's own documentation. Before every release, the server is started from these blocks in Claude Code, Gemini CLI and the OpenAI Agents SDK to confirm it connects. Each client's fine print is in the reference. Claude Code (Anthropic) One command adds SAIHM for all your projects: If the tools don't appear after the first start, give the server more time: MCP_TIMEOUT=60000 claude, or run npx -y @saihm/mcp-server-pro --version once in a terminal and start Claude Code again. claude mcp list shows whether it connected. For Claude Code on the web, see Hosted agent environments. Claude Desktop (Anthropic) Open **Settings > Developer > Edit Config**, add the "saihm" entry inside mcpServers, then quit and reopen Claude Desktop: Claude Desktop starts the server with the Node.js installed on your machine, so install Node.js first. If the tools don't appear the first time, run npx -y @saihm/mcp-server-pro --version in a terminal, then quit and reopen Claude Desktop. Codex CLI (OpenAI) Add this to ~/.codex/config.toml, or to a project's .codex/config.toml: