Saihm MCP Server Pro

SAIHM — memory for AI agents

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 before it leaves your machine. Nobody else can read your memories — not the storage, not SAIHM. There is nothing to switch on. With your key in a file, as in the standard setup, SAIHM also keeps an unencrypted copy of your memories on your own device for fast recall. Only your account can read it, and one setting turns it off.

Start free — one command

npx -y @saihm/mcp-server-pro free-join

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. Its first run downloads the package, which can take a minute before anything appears.
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.

Then add SAIHM to your AI client, restart it, and say "Recall my SAIHM memories." You're running.

No GitHub account? Start at https://saihm.net/free instead: you sign in with Google or Microsoft, and the page gives you your key and the steps to connect your assistant. Follow them, then say "Recall my SAIHM memories." Keep your key safe: it is the only key to your memory. Your key is already active, so skip *"Join SAIHM"*: there is nothing to join, and saying it anyway makes no new key.

Rather let your assistant set it up? Install SAIHM in your AI client first: for Claude Code that is the one command under Claude Code, and the other clients are below. Restart the client, then say "Join SAIHM" to your assistant. It asks whether you already have a SAIHM identity, then 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.19 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.

Adding another AI client on this computer? It uses the key already in ~/.saihm by itself, so don't join again there: add its block, restart it and say *"Recall my SAIHM memories."* Give it the same settings as your first client:

• Your key in another folder or file: set the same SAIHM_HOME, or the same SAIHM_MASTER_SECRET_FILE, in its block.
• A paid plan: add SAIHM_TIER and SAIHM_PAYMENT_METHOD to its block, wherever your key is, ~/.saihm included. Without them the new client signs in on the free plan.

Claude Code (Anthropic)

One command adds SAIHM for all your projects:

claude mcp add --env SAIHM_ENDPOINT_URL=https://saihm.net/mcp --transport stdio --scope user saihm -- npx -y @saihm/mcp-server-pro

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:

{

"mcpServers": { "saihm": { "command": "npx", "args": ["-y", "@saihm/mcp-server-pro"], "env": { "SAIHM_ENDPOINT_URL": "https://saihm.net/mcp" } } } }

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:

[mcp_servers.saihm]

command = "npx" args = ["-y", "@saihm/mcp-server-pro"] env = { SAIHM_ENDPOINT_URL = "https://saihm.net/mcp" } startup_timeout_sec = 60

Check it with codex mcp list, or /mcp inside Codex.

OpenAI Agents SDK (Python)

import asyncio

from agents import Agent, Runner from agents.mcp import MCPServerStdio

async def main(): async with MCPServerStdio( name="saihm", params={ "command": "npx", "args": ["-y", "@saihm/mcp-server-pro"], "env": {"SAIHM_ENDPOINT_URL": "https://saihm.net/mcp"}, }, client_session_timeout_seconds=60, ) as saihm: agent = Agent(name="Assistant", mcp_servers=[saihm]) result = await Runner.run(agent, "Recall my SAIHM memories.") print(result.final_output)

asyncio.run(main())

The 60-second timeout gives the first npx download time to finish. Pass secrets from the environment, never as literals in your code.

Gemini CLI (Google)

Add this to ~/.gemini/settings.json (all projects) or .gemini/settings.json (one project):

{

"mcpServers": { "saihm": { "command": "npx", "args": ["-y", "@saihm/mcp-server-pro"], "env": { "SAIHM_ENDPOINT_URL": "https://saihm.net/mcp" } } } }

Or install the Gemini CLI extension, which carries the same entry: gemini extensions install https://github.com/SAIHM-Admin/saihm-mcp-server-pro.

Run Gemini CLI in a folder you trust, since it starts local servers only there. Check with gemini mcp list, or /mcp inside Gemini CLI.

Since 2026-06-18, Google no longer serves personal Google accounts in the Gemini CLI: signing in with one answers "This client is no longer supported for Gemini Code Assist for individuals". As of October 2026 the Gemini CLI still works with a Gemini API key, or with a Gemini Code Assist Standard or Enterprise licence.

Antigravity CLI (Google)

Add this to ~/.gemini/config/mcp_config.json (all projects) or .agents/mcp_config.json in a project:

{

"mcpServers": { "saihm": { "command": "npx", "args": ["-y", "@saihm/mcp-server-pro"], "env": { "SAIHM_ENDPOINT_URL": "https://saihm.net/mcp" } } } }

Type /mcp inside Antigravity CLI to see whether it connected. If the tools don't appear the first time, run npx -y @saihm/mcp-server-pro --version in a terminal, then reload the server there.

Grok Build (xAI)

Add this to ~/.grok/config.toml, or to a project's .grok/config.toml:

[mcp_servers.saihm]

command = "npx" args = ["-y", "@saihm/mcp-server-pro"] env = { SAIHM_ENDPOINT_URL = "https://saihm.net/mcp" } startup_timeout_sec = 60

Grok Build also picks up an existing saihm entry from ~/.claude.json or a project's .mcp.json, so if you already added it for another client you may not need this step. Check it with grok mcp list, or grok mcp doctor saihm.

GitHub Copilot in VS Code (Microsoft)

Add this to .vscode/mcp.json in a workspace, or to your user mcp.json (run MCP: Open User Configuration). VS Code uses servers here, not mcpServers:

{

"servers": { "saihm": { "type": "stdio", "command": "npx", "args": ["-y", "@saihm/mcp-server-pro"], "env": { "SAIHM_ENDPOINT_URL": "https://saihm.net/mcp" } } } }

Or add it to your user profile from a terminal (bash, zsh or Command Prompt):

code --add-mcp "{\"name\":\"saihm\",\"command\":\"npx\",\"args\":[\"-y\",\"@saihm/mcp-server-pro\"],\"env\":{\"SAIHM_ENDPOINT_URL\":\"https://saihm.net/mcp\"}}"

MCP: List Servers shows the server, and its Show Output action shows the log. If the tools don't appear the first time, run npx -y @saihm/mcp-server-pro --version in a terminal, then restart the server from MCP: List Servers. For the GitHub Copilot cloud agent, see Hosted agent environments.

GitHub Copilot for enterprises (Microsoft)

If your company decides which MCP servers GitHub Copilot may run, an enterprise owner can allow SAIHM:

1. If your company keeps an MCP allowlist, add SAIHM in the same form as the entries already on it, because in a list with command entries, Copilot can require every l