What is the key difference between Iai Personal Memory Engine and Doc Manager?

Iai Personal Memory Engine belongs to the Knowledge & Memory category with local stdio execution, while Doc Manager belongs to the Knowledge & Memory category with cloud HTTP/SSE execution.

How do I install Iai Personal Memory Engine or Doc Manager 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 Iai Personal Memory Engine and Doc Manager free or paid?

Iai Personal Memory Engine operates under a Free / Open Source model (No auth required). Doc Manager operates under a Free / Open Source model (OAuth 2.0).

Which MCP server has more tools and community activity?

Iai Personal Memory Engine lists 9 tools with 2 views and 891 GitHub stars. Doc Manager lists 9 tools with 2 views and 1 GitHub stars.

Can I use both Iai Personal Memory Engine and Doc Manager 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

Iai Personal Memory Engine vs Doc Manager

In-depth architectural comparison of the Iai Personal Memory Engine and Doc Manager 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

Iai Personal Memory Engine

Knowledge & Memory · Local stdio

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

Doc Manager

Knowledge & Memory · Remote HTTP/SSE

Quality: 53/100 (Good) | Auth: OAuth 2.0

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

Which MCP Server Should You Choose?

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.

Explore Iai Personal Memory Engine Details

Choose Doc Manager when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: AZURE_STORAGE_ACCOUNT, AZURE_STORAGE_ACCESS_KEY, RUST_ROCKET_EXACT_ORIGIN, OAUTH_PROVIDER, OAUTH_PUBLIC_BASE_URL, OAUTH_ALLOWED_USERS, MCP_READ_ONLY.

Feature & Specification Comparison

Specification	Iai Personal Memory Engine CodeAbra Knowledge & Memory	Doc Manager giuliohome-org Knowledge & Memory
Summary	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.	Personal document vault on Azure Blob Storage with a built-in MCP server. Client-side AES-256-GCM zero-knowledge encryption: encrypted docs stay opaque to Claude, plaintext docs are fully readable, writable, and searchable from chat.

Tools & Capabilities Breakdown

Iai Personal Memory Engine Tools (9)

memory_recall

Cue-based recall — returns hits **and anti-hits**: memories that *contradict* the cue surface next to the ones that match, so a stale fact can't masquerade as current.

memory_temporal_recall

Time-anchored recall — *"what did I say about pricing in May?"*

memory_recall_structural

Retrieve by the *shape* of a memory (the HD substrate), not just its embedding.

memory_search

Plain text search over the store.

memory_capture

Write a memory explicitly (ambient capture normally does this for you).

memory_contradict

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).

Iai Personal Memory Engine Configuration

mcpServers (Claude Desktop / Cursor)

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

Doc Manager Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "giuliohome-org-doc-manager": {
      "url": "https://claude.ai/api/mcp/auth_callback"
    }
  }
}

Frequently Asked Questions

Iai Personal Memory Engine is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Doc Manager belongs to Knowledge & Memory using remote streaming HTTP/SSE transport. Select Iai Personal Memory Engine when you need capabilities focused on knowledge & memory and Doc Manager when you require tools for knowledge & memory.

More alternatives to Iai Personal Memory Engine More alternatives to Doc Manager Knowledge & Memory category hub