context-lattice
Related Servers
Alternatives to context-lattice
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to query repository structure, symbols, dependencies, Git history, architecture, memory, impact, and guarded edits through a stable MCP interface, returning ranked task-specific evidence within a context budget.48 PyPI8Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to discover, optionally rank, and exactly read bounded source-addressed evidence from large repositories and noisy logs, with local-only privacy controls and quota-aware recovery.2MIT
- 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 gradedqualityFmaintenanceEnables 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.-
- AlicenseCqualityAmaintenanceEnables existing AI assistants to search locally collected web evidence, retrieve cited results, exact quotes, revision IDs, and capture timestamps, and verify source listings through MCP.361MIT
- AlicenseAqualityBmaintenanceExposes bounded MCP tools that let connected coding agents resolve a matter by natural language, search and page through an archived read-only store of Codex and ZCode session history, and write back attributed notes with evidence IDs without auto-merging disagreements.121MIT
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.