keephaven-mcp
Related Servers
Alternatives to keephaven-mcp
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityCmaintenanceEnables AI assistants to read and write a local, encrypted-by-default memory store, so they can share persistent notes and context across sessions and models on your machine.48 npm-- AlicenseNot gradedqualityCmaintenanceEnables AI agents to remember people, projects, places, and topics across conversations under a strict token budget, returning compact handles with expandable details while preserving changes, provenance, and encrypted self-hosted storage.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and write a local-first Markdown/Obsidian notebook via a single capture call that routes text into the right notebook, board, or daily journal entry and returns related notes, alongside search, note and card management, and numeric metric series. Access is governed by per-agent tokens with read/write/admin scopes, optional folder restrictions, and an audit log of every action.675 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides non-custodial, post-quantum encrypted memory for AI agents, enabling portable memory across models with provable erasure.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides persistent memory for AI agents via MCP, enabling agents to store and access notes, files, and session context across sessions and clients while under user control.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to store, read, extend, and share encrypted persistent memory, with pay-per-use access via x402 payments on Base.MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource-action pair: memory file operations, append-only journal operations, search, and status. The boundary between memory_write and journal_append is explicitly clarified, preventing likely misselection.
All tools follow a predictable resource_action pattern: memory_* for file memory and journal_* for journal operations. The convention is consistent and easy to infer.
Eight tools are well-scoped for a memory/filesystem server with an append-only journal. Each tool has a clear role without excessive fragmentation.
The set covers memory file CRUD (read/write/list/delete), identity and quota status, search across memory and journal, and append/read journal lifecycle. The append-only journal intentionally omits edit/delete operations, so the surface is complete for the stated domain.