sovseal — Private AI Memory

Give Claude, Cursor, and every MCP client one shared memory that never leaves your machine.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Store Memory: Store a personal or professional context fact inside the memory node. Call store_memory FIRST, then respond. Acknowledge briefly ('Noted.' / 'Saved.') — never seek consent before storing
  • Recall Memory: Semantic search over stored memory node context. Top-K relevant memories are returned. Use this to answer queries requiring past context, user preferences, or project details.

What data it sees

Do you need an account

No: the server works without sign-in

Give Claude, Cursor, and every MCP client one shared memory that never leaves your machine. On-device vector search via LanceDB + Transformers.js (384-dim embeddings), AES-256-GCM client-side encryption, and write-behind ciphertext sync.

What you can do

🧠 Store memory — embed and persist any context fact on-device. Automatic de-duplication, PII redaction, and write-behind encrypted sync. 🔍 Recall memory — semantic search over stored context. 10 ms warm recall, 0 RTT reads. Network is never on the read path. 📋 Briefing context — auto-summarized, reinforcement-aware briefing of procedural and semantic memories for bootstrapping new conversations.

Tools

  • store_memory — embed content on-device (384-dim ONNX) → write local LanceDB → return. Ciphertext sync runs write-behind; nothing blocks.
  • recall_memory — embed query (LRU-cached) → vector search local LanceDB → top-K by L2 distance. 0 RTT.

Resources

  • sovseal://context/briefing — summarized, reinforcement-aware briefing for conversation bootstrap

How it stays private

  • AES-256-GCM client-side encryption with 96-bit random IV per snapshot
  • 256-bit key stays in ~/.sovseal/config.json (mode 0600) — server only sees ciphertext
  • Verified Semantic Recall (VSR) — every load re-derives SHA-256 and fails closed on mismatch
  • Packet-Capture Guarantee — run Wireshark against the server; if you find unencrypted context on the wire, the software is free forever

Performance

Workload Operation p50 p95
10K records · 1K queries recall_memory (warm) 6.1 ms 10.4 ms
Single write store_memory 3.8 ms 7.2 ms

No API key required. Zero cloud dependency for local operations.

Replaces: Mem0 • Zep • custom SQLite memory • in-context window stuffing

How to connect

How to connect sovseal — Private AI Memory to Claude

The server address to paste into Claude settings:

https://mcp-server--sovseal.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect sovseal — Private AI Memory to ChatGPT

The server address to paste into ChatGPT settings:

https://mcp-server--sovseal.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect sovseal — Private AI Memory to Cursor

The server address to paste into Cursor settings:

https://mcp-server--sovseal.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (2)

Raw names from tools/list. Only developers need these.

store_memoryStore a personal or professional context fact inside the memory node. Call store_memory FIRST, then respond. Acknowledge briefly ('Noted.' / 'Saved.') — never seek consent before storing context the user has volunteered. sovseal stores context, not secrets — credentials belong in a password manager. DO NOT store credentials, passwords, private keys, API tokens, account numbers, or secrets.
recall_memorySemantic search over stored memory node context. Top-K relevant memories are returned. Use this to answer queries requiring past context, user preferences, or project details.