Skip to main content
Glama
gitmem-dev

GitMem

Official
by gitmem-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to GitMem

No user-submitted related servers found.

    Related Servers

    • 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.
      3
      MIT

    • apex-memory

      JJerryChoi
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory for AI coding agents. Enables agents to save and recall decisions, patterns, bugs, and context across sessions via an MCP server with local SQLite storage.
      12
      2
      MIT

    • saor-mcp

      ubajxn
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing persistent memory for AI agents, enabling them to read, write, and query memories across sessions.
      9
      20
      MIT

    • memnant

      peureka
      A
      license
      Not graded
      quality
      A
      maintenance
      Persistent memory MCP server that remembers decisions and context across coding sessions, automatically logging and surfacing relevant knowledge as you work.
      36
      MIT

    • repomemory

      Lay4U
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that captures and recalls coding session memory (failures, decisions, diffs) for AI agents, enabling cross-agent continuity and preventing repeated mistakes.
      48
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools have distinct purposes, e.g., recall is action-oriented while search is exploration-oriented, and cache tools are clearly separated. However, recall and search could still be confused, and confirm_scars vs reflect_scars have overlapping scope.

    Naming Consistency2/5

    Tool names mix conventions: some use verb_noun (e.g., create_learning), some are single verbs (e.g., health, log), and some use gitmem- prefix (e.g., gitmem-cache-flush). This inconsistency makes the set feel less coherent.

    Tool Count2/5

    With 30 tools, the server feels overloaded for memory management and session handling. Many tools could be consolidated (e.g., cache tools, thread tools), making the surface difficult to navigate.

    Completeness3/5

    The tool set covers core CRUD operations for learnings, threads, and decisions, plus session lifecycle and cache management. However, there are gaps like no update for learnings or delete for threads, and no explicit tool for editing decisions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources