jevmem-mcp
Related Servers
Alternatives to jevmem-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceLocal memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.2-

memiofficial
AlicenseNot gradedqualityBmaintenanceGives AI agents a local-first, persistent memory backed by a single SQLite file, letting them save decisions, preferences, and facts, then recall them by meaning or keyword across sessions and projects. Exposes tools for loading pinned context, searching, adding, updating, listing, and deleting memories, so agents stop forgetting between sessions.01Apache 2.0- AlicenseNot gradedqualityAmaintenanceProvides long-term memory for LLMs via local SQLite storage with hybrid search (BM25, vectors, recency decay), enabling AI coding agents to persist and recall memories across sessions without cloud or API keys.53MIT
- AlicenseNot gradedqualityCmaintenanceGives AI coding agents persistent memory by storing observations, decisions, and learnings in a local SQLite database with vector search, full-text search, and a rules engine.4MIT
- AlicenseAqualityCmaintenanceLocal-first memory for AI agents. On-device hybrid retrieval over a single SQLite file.163Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to keep durable long-term memory on the user's own machine, writing sessions and messages into a local SQLite database and retrieving them via keyword, exact, or optional semantic search with surrounding context. Runs entirely offline over stdio, so no cloud service or API key is required to give an agent recall across sessions.1MIT
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes: write, recall, list, forget, pin, stats, flush, and consolidation operations. There is minor overlap between memory_write with pinned=True and memory_pin, and the two 'pending' tools could momentarily confuse, but descriptions make the intended workflows clear.
Every tool uses a consistent snake_case memory_ prefix with readable verb or noun forms (memory_write, memory_recall, memory_pin, memory_forget, memory_consolidate). No naming deviations or mixed conventions.
11 tools is well-scoped for a persistent memory server that includes core CRUD, pinning, listing, stats, and an asynchronous consolidation/synthesis lifecycle. Each tool has a distinct role and none appears redundant.
The core memory lifecycle is well covered: write, recall, list, forget, pin, consolidate, resolve, dismiss, stats, and flush queued writes. A direct content-update tool for an existing memory is missing, so correcting a stored fact requires forgetting and rewriting, but this is a minor workaround gap.