context-lattice
Related Servers
Alternatives to context-lattice
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to retrieve a bounded context packet linking relevant code with prior session evidence, decisions, failures, and fixes from local Codex and Claude Code history.Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to persistently store and retrieve conversation history with hybrid semantic and keyword search, cross-encoder reranking, session filtering, and archiving through MCP tools.-
- AlicenseNot gradedqualityCmaintenanceProvides full-text search and retrieval of archived Claude Code session transcripts, enabling agents to inspect past sessions without loading entire transcripts.MIT
- AlicenseNot gradedqualityAmaintenanceProvides verifiable, append-only context handoffs for Codex and MCP clients, enabling memory persistence and resume across chat sessions.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables searching local OpenAI Codex conversation history by keywords, project, date, or role, listing sessions, and retrieving exact supporting messages through MCP tools.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables semantic search and retrieval of archived AI conversations from multiple providers via the MCP protocol, allowing thread continuation and integration with MCP-capable tools.10MIT
TDQS
Scored across 5 tools
The tools are mostly distinct in purpose: search returns evidence, get resolves a specific citation, explain adds diagnostics, sync ingests data, and status reports health. The only meaningful overlap is between memory_search and memory_explain, since both perform searches, but their different outputs make the distinction usable.
All tools share the consistent memory_ prefix and lower_snake_case convention. The minor deviation is memory_status, which names a state rather than an action, while the other four tools use memory_ followed by a verb-like operation.
Five tools is a well-scoped number for a memory/context server. Each tool covers a distinct part of the workflow: search, resolution, explanation, sync, and status.
The surface covers the core memory lifecycle: retrieval, verification, diagnostics, ingestion, and health monitoring. There is no explicit delete/forget or curation operation, but this is a minor gap because memory appears to be source-backed and managed through the sync tool.