sovseal MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@sovseal MCP ServerWhat do I know about our last retro?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
sovseal MCP Server
An MCP server that gives 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. 0 RTT reads.
Tools
Store Memory (store_memory)
Embeds and persists a context fact inside the local on-device memory node.
Parameters:
content(string, required): A third-person factual statement to store (max 65,536 chars)
Behavior:
Embeds content on-device (intfloat/multilingual-e5-small, 384-dim, ONNX)
Writes to local LanceDB — returns immediately
Ciphertext sync runs write-behind; nothing blocks the caller
Automatically de-duplicates and reinforces existing entries
High-risk PII (SSNs, credit cards, API keys) is automatically redacted before storage
Recall Memory (recall_memory)
Semantic search over stored memory context. Returns top-K relevant memories by L2 distance.
Parameters:
query(string, required): Semantic query string to search past memoriestopK(number, optional): Maximum number of memories to return (1–20, default: 5)
Behavior:
Embeds query on-device (LRU-cached pipeline) → vector search local LanceDB
0 RTT — network is never on the read path
Returns
[score=NUMBER id=ID] textfor each match — smaller score = closer semantic matchReturns
no_matcheswhen the store has no relevant entries
Related MCP server: engram
Resources
Briefing Context (sovseal://context/briefing)
A summarized, reinforcement-aware briefing of procedural, semantic, and recurring memories. Recommended for bootstrapping new conversations with stored user context.
Recent Context (sovseal://context/recent) — Deprecated
Raw list of the most recently stored context facts. Use sovseal://context/briefing instead.
Prompts
Context Injection (/sovseal:context)
System prompt helper that bootstraps a conversation by reading from sovseal://context/recent before the first turn.
Configuration
No API Key Required
sovseal runs 100% on-device. There is no external API key, no cloud dependency, and no account required for local memory operations.
Environment Variables
The server supports the following environment variables:
SOVSEAL_TRANSPORT: Transport mode ("stdio"or"sse", default:"stdio")SOVSEAL_PORT: SSE server port (default:4040)
Installation
Usage with Claude Desktop
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"sovseal-memory": {
"command": "npx",
"args": ["-y", "@sovseal/mcp-server"]
}
}
}Usage with Cursor
Add to your Cursor MCP settings (~/.cursor/mcp.json):
{
"mcpServers": {
"sovseal-memory": {
"command": "npx",
"args": ["-y", "@sovseal/mcp-server"]
}
}
}Usage with VS Code (Copilot / Cline / Roo)
Add to your User Settings (JSON) or .vscode/mcp.json:
{
"servers": {
"sovseal-memory": {
"command": "npx",
"args": ["-y", "@sovseal/mcp-server"]
}
}
}Usage with Windsurf / Zed / OpenCode
{
"mcpServers": {
"sovseal-memory": {
"command": "npx",
"args": ["-y", "@sovseal/mcp-server"]
}
}
}Automatic Onboarding (All Clients)
Detect your IDE, configure global connection settings, and write system instructions automatically:
npx -y @sovseal/mcp-server onboard --write --registerSupported: Cursor, Claude Desktop/Code, Windsurf, VS Code (Copilot/Cline/Roo), Zed, Google Antigravity, and OpenCode.
HTTP/SSE Transport
For always-on autonomous agents, run as a long-lived HTTP/SSE server:
SOVSEAL_TRANSPORT=sse SOVSEAL_PORT=4040 npx -y @sovseal/mcp-serverHosted Endpoint
A hosted HTTP/SSE endpoint is available for web-based MCP clients and marketplace validation:
https://sovseal-mcp-server.barrackbobby1.workers.dev/mcpHow It Stays Private
AES-256-GCM client-side encryption with a 96-bit random IV per snapshot
256-bit key lives in
~/.sovseal/config.json(mode0600) — lose this file, lose every snapshotServer only ever sees ciphertext + SHA-256-derived paths; it cannot read your context
Verified Semantic Recall (VSR) — every load re-derives
sha256(canonicalize(payload))and fails closed on mismatchPacket-Capture Guarantee — run Wireshark or tcpdump against the server; if you find a single byte of unencrypted context on the wire, the software is free forever
Performance
Workload | Operation | p50 | p95 | p99 |
10K records · 1K queries |
| 6.1 ms | 10.4 ms | 21.8 ms |
Single write |
| 3.8 ms | 7.2 ms | 12.5 ms |
First call |
| ~1.2 s | — | — |
All operations are 0 RTT — network is never on the read path.
Build
npm install
npm run buildDevelopment
Prerequisites
Node.js 20.x or higher
npm or pnpm
Setup
Clone the repository:
git clone https://github.com/sovseal/mcp-server.git
cd mcp-serverInstall dependencies:
npm installBuild the project:
npm run buildTesting via MCP Inspector
Build and start the server:
npm run build
node dist/index.jsIn another terminal, start the MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.jsAvailable Scripts
npm run build: Build the TypeScript projectnpm run dev: Watch for changes and rebuildnpm run typecheck: Type-check without emittingnpm run test: Run test suite (Vitest)npm run test:watch: Watch mode testingnpm run bench: Run performance benchmarks
Links
Website: sovseal.com
Documentation: docs.sovseal.com
Trust Center: trust.sovseal.com
Chrome Extension: Chrome Web Store
Full Monorepo: github.com/sovseal/core
License
This server cannot be deployed
Maintenance
Related MCP Connectors
Person-owned AI memory that learns, not just stores — portable context for any MCP client.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Persistent personal memory for AI assistants — save, search, and recall across every MCP client.
Persistent memory for AI agents — log and recall conversation context over MCP.
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceEnables persistent memory storage and retrieval for MCP clients, allowing AI assistants to remember facts and context across conversations.467MIT- AlicenseNot gradedqualityDmaintenanceProvides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.1MIT
- AlicenseNot gradedqualityDmaintenanceA local-first memory MCP server that enables storing, searching, and managing personal memories with hybrid keyword and semantic recall, all on-device.138MIT
- AlicenseNot gradedqualityAmaintenanceProvides MCP tools for AI assistants to add, search, and preload semantic memories that synchronize across devices via encrypted delta sync, enabling seamless cross-device continuity with privacy controls.90MIT