Skip to main content
Glama
yuvalsuede

memory-mcp

by yuvalsuede
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to memory-mcp

No user-submitted related servers found.

    Related Servers

    • am-memory

      danielwanwx
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory for Claude Code — a self-evolving knowledge layer that survives across sessions, grows from every conversation, and surfaces relevant context automatically.
      14
      MIT

    • ORA

      black-dash77
      A
      license
      A
      quality
      D
      maintenance
      Persistent memory + intelligent context for Claude Code. Save and reuse solutions, decisions, and patterns across projects.
      43
      7
      MIT

    • MCP Project Context Server

      aaronfeingold
      A
      license
      B
      quality
      D
      maintenance
      A persistent memory layer for Claude Code that maintains project information, technology stack, tasks, decisions, and session history between coding sessions, eliminating the need to re-explain project context.
      9
      MIT
    • Axme-code by AxmeAI

      Axme-codeofficial

      AxmeAI
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent project memory + architectural decisions + pre-execution safety hooks for Claude Code. Local-only storage, multi-repo workspace, automatic knowledge extraction via background auditor.
      20 npm
      14
      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

    A3.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have distinct purposes, but the retrieval tools (recall, search, related, ask) overlap conceptually. However, each has a clear differentiator: recall lists all, search ranks by keyword, related explores by tag, ask synthesizes an answer. No two tools are truly indistinguishable.

    Naming Consistency3/5

    All tools share the 'memory_' prefix, but suffixes mix verbs (save, delete, search) with nouns (related, consciousness, stats). This inconsistency is noticeable but the command pattern is still readable.

    Tool Count5/5

    10 tools is well within the ideal range for a focused domain. Each tool addresses a distinct aspect of memory management without bloat.

    Completeness4/5

    The core memory lifecycle (init, save, recall, delete, consolidate) is covered, plus useful extras (search, ask, related, stats). Missing an explicit update tool, but delete+re-save works around it.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources