Skip to main content
Glama
otaviosenne

memory-mcp

by otaviosenne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to memory-mcp

No user-submitted related servers found.

    Related Servers

    • Vault MCP Server

      gzlance
      F
      license
      Not graded
      quality
      C
      maintenance
      Built on Obsidian Vault, this MCP server integrates with Claude Code to provide personal knowledge management including note saving, full-text search, code graph extraction, and context resumption.
      1
      -

    • mcp-zettel

      dhruvpatel1706
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides Claude and other MCP clients with persistent memory through a Zettelkasten knowledge base of interconnected markdown notes. It enables LLMs to create, search, link, and reference atomic notes across sessions without requiring manual copy-pasting.
      MIT

    • obsidian-pkm

      AdrianV101
      A
      license
      A
      quality
      B
      maintenance
      This MCP server enables Claude to interact with an Obsidian vault for persistent, structured memory, providing tools for note creation, semantic search, graph traversal, and session memory.
      18
      9 npm
      13
      MIT

    • memcp

      maydali28
      A
      license
      A
      quality
      C
      maintenance
      Persistent memory MCP server that allows Claude to store, organize, and retrieve knowledge across sessions without consuming context window tokens.
      24
      17
      MIT

    • Claude-Atlas-MCP

      dcazman
      A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted MCP server giving Claude persistent memory via entities, observations, history, and reminders, backed by a lightweight Node/SQLite backend.
      8 npm
      1
      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

    B3.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a clearly distinct purpose: save, read, search, list, delete, graph data, stats, and open graph UI. The only slight overlap is between fuzzy search and filtered list, but their descriptions make the difference clear.

    Naming Consistency5/5

    All tool names follow the consistent pattern memory_<action> using lowercase snake_case. The naming is predictable and makes the purpose of each tool immediately understandable.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a memory vault: it covers CRUD operations, search, list, graph data, stats, and a UI opener without unnecessary bloat or thinness.

    Completeness5/5

    The toolset provides full lifecycle coverage for memories (create/update, read, search/list, delete) and also offers graph and stats features for deeper interaction. No obvious gaps are present.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources