Skip to main content
Glama
0Mattias

bettermemory

by 0Mattias
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to bettermemory

No user-submitted related servers found.

    Related Servers

    • AI Dimag by AiDimag

      AI Dimagofficial

      AiDimag
      A
      license
      A
      quality
      A
      maintenance
      MCP server that gives coding agents persistent, verified memory of codebase decisions, conventions, and skills, with evidence-based claims that are re-checked via git hooks and human-gated review. Enables memory search, propose/approve, chat harvesting, and critique across MCP-compatible tools.
      21
      58 npm
      1
      MIT

    • memory-ai-local

      Hsoley1
      F
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that manages developer memory for coding agents, enabling shared project context, permissions, and audit trails across different agents.
      1
      -

    • TIMPS

      TIMPSs
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives AI coding agents persistent memory across sessions, storing architecture decisions, past bugs, and codebase conventions locally.
      14 npm
      MIT

    • cookbook-brain

      dpro10
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents persistent, file-based memory stored as plain markdown files in a local git repository, enabling agents to remember, recall, and build on information across sessions.
      4 npm
      1
      MIT

    • Project Brain

      myczh-1
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP memory server that gives AI assistants durable project memory across coding sessions, storing context, changes, and decisions.
      5 npm
      1
      MIT

    • repomemory

      Lay4U
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that captures and recalls coding session memory (failures, decisions, diffs) for AI agents, enabling cross-agent continuity and preventing repeated mistakes.
      41 npm
      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 18 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action (search vs list vs show; write vs update vs remove vs verify; memory vs episode tier; scope enable/disable). Memory_write_confirm and memory_write_cancel are separate and unambiguous, and memory_audit_turn is explicitly not for model use.

    Naming Consistency5/5

    All tools follow a consistent pattern: memory_<verb> and episode_<verb>, using snake_case throughout. Verbs are descriptive (write, update, remove, verify, search, list, show). No mixed conventions or vague verbs.

    Tool Count4/5

    18 tools is on the heavier side but appropriate for a memory server covering memory lifecycle, scoping, verification, usage tracking, and an episode tier. Each tool has a distinct role; no redundancy. Slightly above the ideal 3-15 range but justified by the breadth of the domain.

    Completeness4/5

    Core CRUD and verification flows are fully covered (write, confirm/cancel, update, remove, verify, restore via reference). However, tools referenced in descriptions like memory_restore, memory_list_tombstones, memory_conflicts, and memory_proposals are not actually exposed, creating minor gaps. Agents can work around these by using memory_remove and memory_write, but the surface is not entirely self-contained.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources