A
licenseNot graded
qualityD
maintenanceProvides persistent long-term memory for LLMs via local SQLite storage and semantic search, enabling recall across sessions without external APIs.
16 npm
5
MIT
longhaul
Related Servers
Alternatives to longhaul
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to keep durable long-term memory on the user's own machine, writing sessions and messages into a local SQLite database and retrieving them via keyword, exact, or optional semantic search with surrounding context. Runs entirely offline over stdio, so no cloud service or API key is required to give an agent recall across sessions.1MIT
whimsicality-mcpofficial
AlicenseBqualityBmaintenanceProvides persistent memory for AI agents, including context storage, facts, plans, RAG search, code snippets, and conversation compaction, enabling state to survive across sessions and processes.1414 npm2MIT- AlicenseNot gradedqualityCmaintenanceProvides persistent memory for AI tools by building a local knowledge graph from conversations, enabling cross-session recall and context awareness without cloud dependencies.9MIT
- -licenseNot gradedqualityNot gradedmaintenanceProvides persistent local memory functionality for AI assistants, enabling them to store, retrieve, and search contextual information across conversations with SQLite-based full-text search. All data stays private on your machine while dramatically improving context retention and personalized assistance.3-
- FlicenseNot gradedqualityDmaintenanceProvides persistent AI agent memory using a local vector database for long-term semantic storage and short-term session scratchpads. It enables low-latency memory operations including search, storage, and bulk management without external cloud dependencies.-
TDQS
A3.9/5.0
Scored across 4 tools
Disambiguation5/5
Each tool serves a distinct, non-overlapping function: compact summarizes the current session, recall searches past memory, timeline lists sessions, and remember stores a fact. No two tools could be confused for one another.
Naming Consistency5/5
All tool names are single lowercase words using a command-like style (compact, recall, timeline, remember). The naming pattern is uniform and intuitive, with no mixed conventions or confusing prefixed/suffixed variations.
Tool Count5/5
Four tools is the right size for a memory-management server. The scope is narrow and each tool covers a necessary function without bloat or redundancy, making the set easy to learn and use.
Completeness4/5
The core memory lifecycle is covered: remember (write), compact (state saving), recall (read/search), and timeline (audit). A possible gap is a delete/forget operation, but for a persistent-memory system this may be intentionally omitted, so the surface is nearly complete.
Maintenance
ActivitySlowing
ResponsivenessNo issues