Skip to main content
Glama
Sign In
timgordontg

engrim

by timgordontg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to engrim

  • agent-memory-os

    yamantaka520
    A
    license
    A
    quality
    B
    maintenance
    Local-first memory engine for AI-agent teams: private/team/project ACL, associative recall, and federated sync across nodes. One SQLite file, no LLM required.
    12
    7
    Apache 2.0

  • sqlite

    nao9net
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP clients to interact with pre-registered SQLite databases using aliases, supporting schema inspection, read-only queries, and data modification via tools.
    106 npm
    MIT

Related Servers

  • memtether by MemTether

    memtetherofficial

    MemTether
    A
    license
    Not graded
    quality
    A
    maintenance
    Cross-client AI memory hub for AI agents. Lets Claude Code, Cursor, Windsurf, and 20+ other clients share one physical SQLite memory database. Features bi-temporal time axes, source attribution, Q-Value usage-based ranking, and FTS5 full-text search with SQLite triggers.
    278 PyPI
    1
    Apache 2.0

  • Sugar

    rSenturk54927
    F
    license
    Not graded
    quality
    A
    maintenance
    Provides a local-first persistent memory layer that lets AI coding agents store, recall, and semantically search project-specific and cross-project knowledge across sessions, so context, decisions, and guidelines survive between conversations. Runs entirely on the user's machine with SQLite and no API keys, and optionally supports autonomous task-queue execution built on the same memory.
    -

  • Sugar

    dzhou56350
    F
    license
    Not graded
    quality
    A
    maintenance
    Gives AI coding agents direct, local-first read/write access to persistent memory — project decisions, preferences, error patterns, research, and cross-project guidelines — retrieved by semantic search backed by SQLite with no API keys or network calls. A companion server also exposes optional autonomous task-queue execution.
    -

  • agentmem

    Thezenmonster
    A
    license
    A
    quality
    D
    maintenance
    Governed 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.
    13
    20 PyPI
    6
    MIT

  • coding-memory-mcp

    ChinaCarlos
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides 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.
    6 npm
    2
    MIT

  • ai-memory

    alphaonedev
    A
    license
    Not graded
    quality
    A
    maintenance
    Persistent 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.
    56
    Apache 2.0
Deploy Server
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources