Skip to main content
Glama
AbdulqaderAhmed

memory-manager-mcp

by AbdulqaderAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to memory-manager-mcp

No user-submitted related servers found.

    Related Servers

    • Sugar

      Sitas17424
      F
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP memory server that lets AI coding agents store, search, and recall project-specific and cross-project knowledge, so architecture decisions, preferences, error patterns, and coding guidelines persist across sessions. It also exposes optional task-queue tools for handing off autonomous work that draws on the same stored context.
      -

    • 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.
      21 npm
      2
      MIT

    • sugar

      JeanKwon23467
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to store, search, and recall persistent project and cross-project memories locally over MCP, keeping architectural decisions, conventions, and error patterns available across sessions. Also optionally exposes a task server for autonomous task execution driven by that same memory store.
      -

    • memory-ai-local

      Hsoley1
      F
      license
      Not graded
      quality
      D
      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
      -

    • coster

      savai15
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides offline-first, persistent memory for AI coding assistants. It captures project decisions and conventions into a local SQLite database and syncs them to tool-specific memory files like CLAUDE.md and AGENTS.md.
      4 npm
      MIT
    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

    A3.6/5.0

    Scored across 16 tools

    Disambiguation3/5

    Tools like get_project_context and get_current_task both surface the current task, and save_memory can also store decisions, overlapping with record_decision. Descriptions help, but the boundaries are not always crisp.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_, save_, create_, update_, start_, finish_, delete_, clear_) with no mixed casing or irregular verbs. Naming is fully predictable.

    Tool Count4/5

    At 16 tools, the server is on the higher end of typical tool counts, but each tool targets a distinct facet of memory management (context, memories, tasks, decisions, handoffs, sessions). A few could be merged, but the scope is defensible.

    Completeness3/5

    The server covers memory CRUD, task management, decision logging, handoffs, and sessions, but lacks per-memory update/delete operations and task/decision deletion. These gaps can be worked around but represent notable missing functionality.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources