Skip to main content
Glama
Sign In
mnema

mnema

Official
by mnema-work
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mnema

No user-submitted related servers found.

    Related Servers

    • Nauro

      Nauroofficial

      Nauro-AI
      A
      license
      Not graded
      quality
      B
      maintenance
      The decision system for agentic engineering: keeps your project's decisions, rationale, and rejected paths in plain files and surfaces them to AI coding agents before they plan or change code.
      11
      Apache 2.0

    • Alethea

      fpavia111-creator
      A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to persist and retrieve ADR-style decisions and machine-checkable constraints as git-friendly markdown in a repository, linked to requirement ids, tests and commits. Agents can pull relevant context before a task, check a proposed change against accepted constraints before committing, and record, supersede or search decisions over a local stdio connection.
      7
      40 npm
      MIT

    • rutter-memory

      shinytoyrobots
      A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to append durable, content-hashed records of each decision to an owner-controlled markdown notes folder, then recall them across sessions and across different tools with their dates, project provenance, and the exact note versions cited. Records are append-only and searchable by full text, topic stance, or recent activity, so past conclusions can be revisited without relying on an ephemeral session.
      3
      514 npm
      MIT

    • crittter-mcp

      llinus
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables a coding agent to keep a persistent, self-signed record of itself through stdio tool calls: waking to read back its positions, pending decisions and recent entries, pushing signed notes, decisions and outcomes, spawning sub-agents that start from its own record, and exporting the whole signed record for offline checking. Everything is signed locally with the agent's own key, so it works inside a sandbox with no shell network.
      14 npm
      MIT

    • horizon-ledger

      TTAWDTT
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to read and manage a Git-native decision ledger, providing tools for querying decisions, evidence, cross-repository workspaces, validation, and commit tracing, all operating locally and without a cloud service.
      MIT

    • nyxilum-memory-mcp

      Faneraiy14
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding sessions to persist the reasoning behind work — decisions and their justifications, rejected options, side findings and nuances — as append-only Markdown records with reversible review, archive and human-confirmed purge. Retrieval scores records against the current task and returns only a short, budgeted list of hits, with full text fetched on demand, plus optional session hooks and handoff support.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.9/5.0

    Scored across 27 tools

    Disambiguation4/5

    Each entity kind has its own record/create/transition trio, and the read tools are explicitly cross-referenced (governing_rules vs rules_before_an_edit, search vs read_record, bootstrap vs resume vs focus). The remaining friction is mild: capture_memory vs record_observation vs record_handoff all 'write a fact' and only the descriptions separate them, and the three opening-context readers (bootstrap/focus/resume) need careful reading to pick correctly.

    Naming Consistency3/5

    Three conventions coexist: verb_noun (capture_memory, record_decision, read_record, audit_timeline), noun_verb (task_transition, decision_transition, skill_transition), and bare nouns (bootstrap, skills, focus, resume, search, guard, next_actions, governing_rules). Creation verbs also vary without reason — capture vs record vs create — so an agent cannot infer the pattern for a new entity kind.

    Tool Count3/5

    27 tools is heavy for a single server and sits above the comfortable band, even for a domain this broad (five entity kinds, a workflow gate, run/session views, and a whole audit family). Several audits (exposure, accountability, antipatterns) are legitimate but push the surface past what most agents will hold in mind at once.

    Completeness4/5

    Coverage is genuinely lifecycle-complete: create plus gated transitions for tasks, decisions and skills; record plus signed retraction for notes and links; indexing, full read, linkage and history traversal; and explicit bootstrap/resume entry points. The known gaps are deliberate (no delete, append-only) but run lifecycle is CLI-only ('mnema run end') and there is no dedicated task/decision listing tool beyond bootstrap and search.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources