engrim
Related Servers
Alternatives to engrim
- AlicenseAqualityAmaintenanceLocal-first memory engine for AI-agent teams: private/team/project ACL, associative recall, and federated sync across nodes. One SQLite file, no LLM required.126Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to interact with pre-registered SQLite databases using aliases, supporting schema inspection, read-only queries, and data modification via tools.57 npmMIT
Related Servers
- AlicenseAqualityDmaintenanceGoverned memory for coding agents with trust lifecycle, conflict detection, staleness tracking, and health scoring. SQLite + FTS5, zero infrastructure. Works with Claude Code, Cursor, Codex, Windsurf.1335 PyPI4MIT
- AlicenseNot gradedqualityBmaintenanceProvides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.36 npm2MIT
- AlicenseNot gradedqualityAmaintenancePersistent memory for any AI assistant. Zero token cost until recall. Stores memories in local SQLite, ranks by 6-factor scoring, returns results 79% smaller than JSON. Works with Claude, ChatGPT, Grok, Cursor, Windsurf, and any MCP client.53Apache 2.0
- AlicenseAqualityAmaintenanceLocal-first memory for AI agents. On-device hybrid retrieval over a single SQLite file.162Apache 2.0
- AlicenseBqualityAmaintenanceLocal-first, auditable memory for Codex, Claude Code, and MCP clients. It stores scoped user/project memory in SQLite or Postgres, serves read-only recall and inspection tools by default, and supports opt-in governed writeback with review and forget controls.8230 npm19MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents like Codex, Grok Build, and Antigravity to share persistent local memory, preferences, project context, tasks, and handoffs using Markdown and SQLite.1MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: context retrieval, semantic search, writing records, and pre-clear review. There is no overlap between reading curated context, searching all memory, adding new records, or checking for unsaved decisions.
All tools share the engrim_ prefix and use short, consistent verb-like suffixes (context, recall, add, review). Minor deviation: 'context' and 'recall' are nouns/verbs rather than a strict verb_noun pattern, but the naming is predictable and readable.
Four tools is a well-scoped set for a memory server: read curated context, search all memory, write new memory, and review unsaved history. Each tool earns its place with no redundancy.
The core memory lifecycle is covered: add, recall, context, and pre-clear review. A minor gap is the lack of explicit update/delete operations for correcting or removing stale records, but agents can work around this by adding superseding records.