Skip to main content
Glama
nworks3d

thor-memory-bible

by nworks3d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to thor-memory-bible

  • cogmem

    dcondrey
    A
    license
    A
    quality
    F
    maintenance
    Self-improving, verifiable memory for AI coding agents. Learns how you work, stops repeating mistakes, models each project, recalls the right lesson at the right moment. Every memory is signed and tamper-evident. Local-first.
    8
    2
    Apache 2.0

  • GoodMemory

    hjqcan
    A
    license
    B
    quality
    A
    maintenance
    Local-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.
    8
    145 npm
    18
    MIT

  • memini

    lumayapartners
    A
    license
    A
    quality
    B
    maintenance
    Local-first project memory for AI coding agents. Records failed attempts, fragile files, and decisions per repo, and warns the agent via hooks before it repeats a recorded mistake.
    6
    42 npm
    MIT

  • Sentinela MCP

    luclinocruz
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides coding agents with durable, cross-session lessons-learned memory, enforcing that success or failure verdicts can only come from human approval, human correction, or objective metrics—never from the agent itself.
    Apache 2.0
  • @team-monet/monet by team-monet

    @team-monet/monetofficial

    team-monet
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides a local-first memory layer for coding agents, storing principles, rules, and corrections on-device and surfacing them at the moments they apply so agents act on the intended outcomes without sending data to the cloud.
    18,420 npm
    1
    AGPL 3.0

  • AgentRecall

    AkbarDizaji
    A
    license
    Not graded
    quality
    A
    maintenance
    A local-first memory for AI coding agents. AgentRecall turns the feedback and failures you run into while coding into reusable rules, then serves the right ones back — on the command line or directly to Claude Code over MCP. Everything stays on your machine: no cloud sync, no web UI, no API keys.
    9
    MIT

Related Servers

  • rsi-boot

    Apollo-lwx
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI coding assistants to persist and recall project-specific conventions, prohibitions, and repair lessons locally, with approved rule injection before tasks and no external API calls.
    MIT

  • Nahuali

    Arakiss
    F
    license
    Not graded
    quality
    A
    maintenance
    Local-first memory for AI agents with evidence-backed recall, deterministic trust verdicts, self-inspection, and a tamper-evident audit history.
    3
    -

  • al-buddy-memory-mcp

    flytomoon
    A
    license
    Not graded
    quality
    A
    maintenance
    Gives AI agents governed, provenance-tagged memory where facts are invalidated rather than deleted and every recall result carries validity dates, confidence, and replacement links. Stores memory in a local SQLite file with tools for remembering, recalling, invalidating, and pinning facts, plus policy enforcement and an audit trail.
    1,295 npm
    3
    Apache 2.0
  • docmancer by docmancer

    docmancerofficial

    docmancer
    A
    license
    A
    quality
    B
    maintenance
    Local-first memory for coding agents. Discovers the memory, instructions, and rules Claude Code, Codex, and Cursor already wrote on your machine, combines them into one canonical Markdown tree, and serves grounded, cited recall through tools like ask_memory and canonical_memory.
    20
    222 PyPI
    126
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 16 tools

Disambiguation5/5

Each tool occupies a clearly distinct niche, and descriptions explicitly cross-reference each other to prevent misselection (get vs lookup vs history, outline vs where_used vs search_code, mark vs revise vs retract). The read/write/judge/lane boundaries are unambiguous.

Naming Consistency4/5

All names are lowercase and consistently styled, but the set mixes bare verbs (mark, pin, revise, remember, retract) with nouns (status, history, library) and only a couple of multi-word names (search_code, where_used). Readable and predictable enough, with minor convention drift.

Tool Count4/5

At 16 tools it sits at the upper edge, but the domain spans memory CRUD, bindings, conflict resolution, a separate library lane, and a code index, so each tool earns its place. No obviously redundant tools.

Completeness4/5

Full item lifecycle is covered (remember/revise/retract/get/lookup/history), plus binding management (pin/unpin), conflict resolution (resolve), judgement (mark), the library lane (shelve/library), and code search. Only minor gaps, such as no explicit bulk listing of bindings or pinned items, which agents can work around via status/lookup.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources