What is the key difference between Saihm MCP and Iai Personal Memory Engine?

Saihm MCP belongs to the Knowledge & Memory category with local stdio execution, while Iai Personal Memory Engine belongs to the Knowledge & Memory category with local stdio execution.

How do I install Saihm MCP or Iai Personal Memory Engine in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Saihm MCP and Iai Personal Memory Engine free or paid?

Saihm MCP operates under a Free / Open Source model (API Key required). Iai Personal Memory Engine operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Saihm MCP lists 8 tools with 3 views and 1 GitHub stars. Iai Personal Memory Engine lists 9 tools with 2 views and 870 GitHub stars.

Can I use both Saihm MCP and Iai Personal Memory Engine together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Saihm MCP vs Iai Personal Memory Engine

In-depth architectural comparison of the Saihm MCP and Iai Personal Memory Engine MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Saihm MCP

Knowledge & Memory · Local stdio

Quality: 57/100 (Good) | Auth: API Key required

Iai Personal Memory Engine

Knowledge & Memory · Local stdio

Quality: 67/100 (Great) | Auth: No auth required

Verdict Summary: Choose Saihm MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Iai Personal Memory Engine if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Saihm MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: SAIHM_ENDPOINT_URL, SAIHM_AUTH_HEADER.
Primary tools included: saihm_remember, saihm_recall, saihm_forget.

Explore Saihm MCP Details

Choose Iai Personal Memory Engine when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: memory_recall, memory_temporal_recall, memory_recall_structural.

Feature & Specification Comparison

Specification	Saihm MCP SAIHM-Admin Knowledge & Memory	Iai Personal Memory Engine CodeAbra Knowledge & Memory
Summary	Sovereign, encrypted, persistent memory for AI agents. Eight MCP tools — remember, recall, forget (GDPR Art. 17 erasure), share. Anchored on COTI V2 mainnet. Apache-2.0. Install: npx -y @saihm/mcp-server.	Local memory daemon for any MCP-over-stdio client with three-tier storage (episodic/semantic/procedural). Own SQLite + hnswlib store (Hippo) with bge-small-en-v1.5, MIT-licensed community-detection reranking (MOSAIC), and sleep-cycle consolidation. AES-256-GCM encrypted at rest, no telemetry. Verbatim recall >=99% and post-contradiction Rescue@10 1.000 at honest scale. Ambient capture via shell hooks. Windows support in beta.

Tools & Capabilities Breakdown

Saihm MCP Tools (8)

saihm_remember

Store information in SAIHM persistent encrypted memory. Use this when a fact, decision, or piece of context should outlive the current session. Returns the cell id that saihm_forget takes.

saihm_recall

Retrieve memories from the SAIHM encrypted store; the operator decrypts and returns plaintext, and this client holds no keys. Use at the start of a session, or whenever past context is needed. Pass a keyword to filter, or leave empty to load all.

saihm_forget

Cryptographically erase one memory by its cell id (GDPR Art. 17). Destroying the key makes the content unreadable to everyone, the operator included. Irreversible: use it when erasure is the intent, not to tidy a working set.

saihm_status

Show the current SAIHM session: agent identity, tier, the prs and bfsi scores, storage by tier, and sharing state, as far as the operator reports them — a non-custodial operator cannot see stored-byte totals. Use it to check the agent identity, custody mode, and what the operator reports about storage and sharing.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Saihm MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "saihm-admin-saihm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@saihm/mcp-server"
      ],
      "env": {
        "SAIHM_ENDPOINT_URL": "YOUR_SAIHM_ENDPOINT_URL_HERE",
        "SAIHM_AUTH_HEADER": "YOUR_SAIHM_AUTH_HEADER_HERE"
      }
    }
  }
}

Iai Personal Memory Engine Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "codeabra-iai-personal-memory-engine": {
      "command": "uvx",
      "args": [
        "iai-pme"
      ]
    }
  }
}

Frequently Asked Questions

Saihm MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Iai Personal Memory Engine belongs to Knowledge & Memory using local stdio subprocess. Select Saihm MCP when you need capabilities focused on knowledge & memory and Iai Personal Memory Engine when you require tools for knowledge & memory.

More alternatives to Saihm MCP More alternatives to Iai Personal Memory Engine Knowledge & Memory category hub Canonical compare URL