memory-ultra-rag-mcp
Related Servers
Alternatives to memory-ultra-rag-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides a drop-in MCP memory server over stdio using a local SQLite store, enabling agents to store, search, and audit memory with provenance, scoped access, and contradiction tracking without requiring API keys, LLMs, or embedding providers.258 npm16Apache 2.0
- AlicenseNot gradedqualityCmaintenanceServes local-first project memory over stdio, exposing tools to inspect project state, search and retrieve context, report memory, and create Git-aware checkpoints for coding agents.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLocal MCP server exposing the dek-memory hybrid memory engine over stdio, with optional ChatGPT tools for managing account memories via a browser profile.MIT
- AlicenseNot gradedqualityAmaintenanceServes a unified local memory bank over a stdio MCP server, exposing five tools and one resource so any MCP-capable harness can list, search, and read memories imported from Claude Code, Codex, Cursor, Kimi Code, and ZCode. It gives agents a single read-only view of user preferences, feedback, project state, and reference material stored as plain Markdown files.MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to read, navigate, and query long-term memory stored as readable, reviewable source files, exposing paged catalogs, indexed searches that explain their misses, bounded relation traces, link diagnostics, raw file access, and preflight checks of drafts against MUST constraints. It serves this read-only by default over stdio so any MCP client can start from a memory catalog and keep reading toward the answer instead of relying on a single similarity guess.1MIT
- AlicenseNot gradedqualityAmaintenanceExposes repo-native, self-verifying memory to coding agents over stdio MCP, letting them recall ranked past decisions, record new claims with verifiable receipts, and check the health and stats of stored memory. Keeps agent context honest by surfacing memories whose evidence no longer holds.5 npmMIT
TDQS
Scored across 4 tools
The four tools have largely distinct roles: record_memory creates/overwrites a statement, recall_memory searches, forget_memory removes, and record_handoff manages session handoffs. There is minor overlap because record_handoff also writes memory, but the descriptions clearly differentiate it by its replace-last semantics and session-focused purpose.
All names follow a consistent snake_case verb_noun pattern: record_memory, recall_memory, forget_memory, record_handoff. The convention is predictable and easy to parse.
Four tools is well-scoped for a memory server, covering the core lifecycle operations (record, recall, forget) plus a specialized handoff tool. No tool feels redundant or missing for the stated purpose.
The surface covers create, read, delete, and session handoff, but lacks a direct update operation. Agents can work around this by forgetting the old statement and recording a new one, so the gap is minor but noticeable.