Saihm MCP

What SAIHM-Admin/saihm-mcp MCP server does

SAIHM-Admin/saihm-mcp MCP server adds persistent memory operations to MCP-capable agents. Agents can save facts, decisions, or other context for later sessions, retrieve stored memories, erase a memory cell, and manage narrowly scoped access for other agents. The package exposes eight MCP tools: saihm_remember, saihm_recall, saihm_forget, saihm_status, saihm_share, saihm_revoke_share, saihm_governance_propose, and saihm_governance_vote.

The memory model is designed around user-controlled data. Forgetting a cell destroys its key and is irreversible, while revoking a share stops future access without retracting content that a recipient already read. Sharing identifies recipients by hexadecimal agent-ID hashes and can use temporary, permanent, or syndicate access with read, write, or read-write scope.

How it works

SAIHM-Admin/saihm-mcp MCP server communicates over MCP with the SAIHM operator URL supplied in its environment. It does not implement cryptography, keep the memory store, or run the protocol itself. The configured operator handles those functions and returns the results to the client. The package does not transmit raw private keys.

The implementation is intended for a custodial operator that performs cryptography server-side. The hosted SAIHM service at saihm.coti.global is described as non-custodial and therefore is not suitable for this crypto-free package; that service requires a client-side cryptographic package instead. The operator stack is described as running on COTI V2 mainnet.

Read-only tools include recall and status. The forget, share, revoke-share, and governance operations can change state. Governance proposal and voting calls are disabled by default and return an error unless the configured operator enables them. When enabled, proposals return an ID for voting, and vote weight uses the governance-token balance at the proposal snapshot epoch.

Setup and configuration

Install the package with:

npx -y @saihm/mcp-server

Configure these environment variables in the MCP host's server definition or export them before launch:

• SAIHM_ENDPOINT_URL: URL of the custodial SAIHM operator MCP endpoint.
• SAIHM_AUTH_HEADER: authorization header value expected by that operator, typically a bearer token.

The server reads process environment variables and does not load .env files or configuration from disk. Until both an endpoint and suitable authentication are configured, the tools have nowhere to send requests and will return an error. A Claude Desktop configuration can launch the package through npx and provide the variables in its env block.

Tools and capabilities

SAIHM-Admin/saihm-mcp MCP server supports these workflows:

• Store a new encrypted memory and receive its cell ID.
• Recall all memories or filter them with a keyword.
• Permanently erase a cell by ID under the described GDPR Article 17 workflow.
• Inspect reported agent identity, tier, scores, storage information, and sharing state.
• Grant selected shards to another agent without copying the memory.
• Revoke a sharing contract by contract ID.
• Submit governance proposals or cast votes when the operator has enabled governance.

Each tool includes MCP annotations such as read-only, destructive, idempotent, and open-world hints, along with a human-readable title. These annotations let compatible hosts apply confirmations and help agents choose tools appropriately.

Limitations and notes

This package requires an operator endpoint and token; it is not a standalone encrypted database. It also cannot use the hosted non-custodial service as-is because it has no client-side cryptography. Use the companion client-side package for that deployment model.

Treat saihm_forget as destructive: key destruction makes the memory unreadable and cannot be undone. Revoking a share affects future reads only. Governance calls should be expected to fail on operators where the feature remains disabled. The package is licensed under Apache-2.0.