Log inSubmit server
Saihm MCP Server Pro logo

Saihm MCP Server Pro

Encrypted, portable memory for AI agents with local sealing, sharing, revocation, governance, and irreversible deletion.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Saihm MCP Server Pro

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "saihm-mcp-server-pro": {
      "command": "npx",
      "args": [
        "-y",
        "@saihm/mcp-server-pro"
      ],
      "env": {
        "SAIHM_ENDPOINT_URL": "YOUR_VALUE_HERE",
        "SAIHM_MASTER_SECRET_FILE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 9 tools correctly (10d ago).

Overview

The saihm-mcp-server-pro MCP server connects AI clients to SAIHM's encrypted memory service through a local Node.js MCP process. It lets agents remember, recall, forget, share, and revoke memory cells, plus propose and vote on governance actions. Memory is encrypted on the user's machine before storage, while read and write operations open or seal cells client-side. Reach for it when an agent needs memory across sessions, models, vendors, or authorized users.

Use cases

  • Retain agent memory across sessions and model providers
  • Recall encrypted memory cells from an AI client
  • Share selected memories with another user's agent
  • Revoke access to previously shared memory
  • Propose and vote on memory governance actions

Key features

  • Client-side memory sealing and opening
  • Portable memory across assistants and vendors
  • Authenticated memory sharing and revocation
  • Irreversible memory deletion
  • Governance proposals and voting
  • Read-only status inspection

Tools9

What Saihm MCP Server Pro lets your agent do. Expand a tool for its parameters.

Verified live~2.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

12/17 checks healthy over the last 91d

What it can do

From the 9 tools this server returned when we ran it; 9 declare their own safety hints.

Can delete or modify data · 2Handles credentials · 2Makes network requests · 9Read-only tools · 7
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age130 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · @saihm/mcp-server-pro (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commit11d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed9Callable tools this server registers over MCP.

How Saihm MCP Server Pro works

What saihm-mcp-server-pro MCP server does

The saihm-mcp-server-pro MCP server gives AI agents access to portable memory managed through SAIHM. It is intended for retaining information between sessions and making that information available when changing assistants, models, or vendors. The local process communicates with the SAIHM endpoint while keeping memory encryption on the user's machine.

Each memory cell is sealed before it is sent for storage. The server also supports sharing a cell with another user's agent and withdrawing that access later.

How it works

The package runs locally through Node.js and is started by an MCP client with npx. A client supplies the SAIHM endpoint URL, and the server uses an identity key created during the free-join process or supplied through a protected key file. The join flow creates a key on the machine and uses a browser-based approval step.

The saihm-mcp-server-pro MCP server performs sealing and opening on the client side. saihm_remember writes a sealed memory cell, while saihm_recall reads cells that belong to the user or have been shared with them. The storage service therefore receives encrypted content rather than the plaintext memory described to the agent.

Setup and configuration

Node.js 20 or later is required. The package is available as @saihm/mcp-server-pro on npm. A typical local configuration starts it with npx -y @saihm/mcp-server-pro and sets SAIHM_ENDPOINT_URL to https://saihm.net/mcp.

To begin, run npx -y @saihm/mcp-server-pro free-join. The command creates or reuses a machine key, displays a link and short code, and waits for browser approval through GitHub. Users without GitHub can obtain a key through the SAIHM website and point SAIHM_MASTER_SECRET_FILE to a file containing it. The documentation advises against placing the key itself directly in client settings.

The README provides configuration examples for Claude Code, Claude Desktop, Codex CLI, Gemini CLI, VS Code, Cline, Cursor, Windsurf, and the OpenAI Agents SDK. First startup may need a longer timeout because npx downloads the package.

Tools and capabilities

The available MCP tools are:

  • saihm_remember: seals and writes a memory cell from the client.
  • saihm_recall: read-only access to the user's cells or cells shared with them.
  • saihm_forget: permanently erases a memory and cannot be undone.
  • saihm_status: reports status without modifying memory.
  • saihm_share: creates an end-to-end-authenticated sharing grant.
  • saihm_revoke_share: withdraws an existing sharing grant.
  • saihm_governance_propose: opens a governance proposal.
  • saihm_governance_vote: casts a vote on a governance proposal.

These operations cover personal memory, controlled sharing, access withdrawal, and the governance actions exposed by the service.

Limitations and notes

The server requires a local Node.js installation and an MCP client that can launch a stdio server. Joining requires a browser and an account-based approval flow unless a key is obtained through the alternate website process. The memory key should be kept in a file readable only by the intended user.

Deletion through saihm_forget is destructive and irreversible, so agents should not invoke it without clear confirmation. A shared cell can be read by the recipient while the grant is active; saihm_revoke_share is provided to withdraw that grant. The documentation describes encrypted storage and client-side sealing, but does not specify recovery behavior for a lost key.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Saihm MCP Server Pro

saihm-mcp-server-pro is an MCP server that connects AI clients to SAIHM's encrypted memory service. Its main tools remember and recall memory cells, forget them irreversibly, check status, share and revoke access, and create and vote on governance proposals. Memory is sealed and opened on the user's machine before storage or retrieval.

Install it by configuring your MCP client to run `npx -y @saihm/mcp-server-pro`; Node.js 20 or later is required. Set `SAIHM_ENDPOINT_URL` to `https://saihm.net/mcp`, then restart the client. The README includes client-specific examples for local stdio configurations.

Create a key by running `npx -y @saihm/mcp-server-pro free-join`. The command creates or reuses a key on the machine and asks you to approve a short code in a browser through GitHub. Alternatively, obtain a key from the SAIHM website and use `SAIHM_MASTER_SECRET_FILE`.

Yes, saihm-mcp-server-pro works with Cursor through a local `mcpServers` configuration. Add an entry that starts `npx -y @saihm/mcp-server-pro`, set `SAIHM_ENDPOINT_URL`, and restart Cursor. The same configuration pattern is documented for Cline and Windsurf.

Yes, `saihm_forget` permanently deletes a memory and the operation is irreversible. Use it only when the agent or user has clear authorization to erase the selected cell. The server also provides read-only recall and status tools for non-destructive operations.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSaihm MCP Server Pro AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/saihm-mcp-server-pro?style=directory)](https://allmcps.com/mcp/saihm-mcp-server-pro)
HTML Embed
<a href="https://allmcps.com/mcp/saihm-mcp-server-pro"><img src="https://allmcps.com/api/badge/saihm-mcp-server-pro?style=directory" alt="Saihm MCP Server Pro on AllMCPs" /></a>