OpenExp
Related Servers
Alternatives to OpenExp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenancePersistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.1650 npm7MIT
- AlicenseBqualityAmaintenancePersistent, local memory for AI coding agents that learns how you work, not just what you said. Supports Claude Code, Codex CLI, Cursor, and any MCP client.77758 PyPI71MIT
- AlicenseAqualityCmaintenanceLocal-first memory for Claude Code and any MCP client: hybrid vector + keyword search and a bi-temporal knowledge graph in one SQLite file. Local embeddings, no API key, $0/token.51168 npm2PolyForm Noncommercial 1.0.0
- AlicenseAqualityAmaintenancePersistent local memory for Claude Code that indexes every session's JSONL file verbatim into SQLite + ChromaDB. Exposes 17 MCP tools for semantic recall, deterministic file replay, and fuzzy "do you remember when..." queries across your entire session history — no API calls, nothing leaves the machine.17367 PyPI14MIT
- AlicenseNot gradedqualityBmaintenancePersistent memory for AI coding agents that stores and recalls preferences, decisions, and conventions via semantic similarity, with zero cloud dependencies and plug-and-play MCP integration for Claude Code.Apache 2.0
- AlicenseAqualityAmaintenanceMCP-native persistent memory layer for AI agents across Claude Code, Cursor, VS Code, and OpenClaw. Powered by hybrid vector search, BM25, and cross-encoder reranking with a published 73.1% LoCoMo benchmark accuracy.84Apache 2.0
TDQS
Scored across 5 tools
Each tool maps to a distinct concern: memory system health, memory search, memory creation, prediction logging, and outcome resolution. The prediction/outcome pair is clearly separated by their lifecycle roles.
search_memory, add_memory, log_prediction, and log_outcome all follow a verb_noun pattern. memory_stats deviates by starting with a noun, making get_memory_stats the more consistent equivalent.
Five tools is appropriately scoped for a memory plus prediction-logging server. Each tool covers a necessary function without redundancy.
The memory surface covers add, search, and health stats, while predictions cover both logging and outcome resolution. Missing prediction retrieval/listing and memory mutation/deletion are minor gaps rather than critical dead ends.