Calyx MCP
Related Servers
Alternatives to Calyx MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceHebbian memory system for AI coding agents that learns file associations, error-fix patterns, and tool sequences, enabling instant recall of related context to save tokens.29 npm13MIT
- FlicenseAqualityBmaintenanceGives coding agents a memory of codebases by searching repositories using semantic similarity and structural call/import graphs, enabling reuse of proven patterns and reducing token usage.61-
- FlicenseNot gradedqualityBmaintenancePersistent, self-curating memory for coding agents. It enables local, zero-cost context recall through MCP tools with hybrid retrieval and autonomous consolidation.-
- AlicenseBqualityCmaintenanceEnables programming agents to capture errors and conversation signals, reflect on root causes, consolidate reusable skills, and retrieve relevant context for future tasks, providing a self-learning memory loop.15MIT
- AlicenseAqualityFmaintenanceSelf-improving, verifiable memory for AI coding agents. Learns how you work, stops repeating mistakes, models each project, recalls the right lesson at the right moment. Every memory is signed and tamper-evident. Local-first.82Apache 2.0
- AlicenseBqualityAmaintenanceEnables local AI coding agents and web agents to store, retrieve, and search memories using hybrid semantic, lexical, and knowledge-graph ranking with cognitive decay modeling in a local on-device database.15MIT
TDQS
Scored across 5 tools
Each tool has a distinct action: check_code_reflex evaluates proposed code, query_associative_memory performs raw similarity search, remember_code_outcome writes, inspect_memory_state reports stats, and reset_memory clears. The only mild overlap is between check_code_reflex and query_associative_memory, both of which read the associative store, but their input/output contracts differ enough to disambiguate.
All five names are snake_case verb_noun constructions (check_code_reflex, remember_code_outcome, query_associative_memory, inspect_memory_state, reset_memory), giving a predictable pattern. Minor deviation: reset_memory and inspect_memory_state drop the '_code_' qualifier used by the others, but readability remains high.
Five tools is well-scoped for a lightweight associative memory service, with each tool mapping to a clear lifecycle operation (write, read, evaluate, inspect, reset). No redundant or filler tools are present.
The surface covers the full memory lifecycle: write (remember_code_outcome), read/search (query_associative_memory, check_code_reflex), introspection (inspect_memory_state), and deletion (reset_memory). Minor gaps like bulk import/export or targeted single-memory deletion exist but are not blocking for the stated purpose.