Skip to main content
Glama
emasoudy

mem0-custom-mcp

by emasoudy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mem0-custom-mcp

No user-submitted related servers found.

    Related Servers

    • Claude Memory

      AmmarJawad
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides Claude Code with persistent memory across sessions, including session checkpoints, image persistence, and bidirectional sync with claude.ai projects.
      1
      MIT

    • mem0-mcp

      andresmorales07
      A
      license
      A
      quality
      A
      maintenance
      A server that wraps a self-hosted mem0 REST API as MCP tools for Claude Desktop and Claude Code, enabling memory operations such as adding, searching, and managing memories via natural language.
      6
      1
      MIT

    • tech-memory-mcp

      myx0423
      A
      license
      Not graded
      quality
      D
      maintenance
      A MCP server that gives Claude Code and other AI assistants long-term memory by automatically extracting technical knowledge from conversations and retrieving relevant experiences in future sessions.
      3 npm
      MIT

    • awhm-mcp

      juderosendev
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives Claude Code persistent, fully local long-term memory across conversations, with tools to query, log, consolidate, snapshot, and delete memories without any LLM calls.
      MIT

    • Personal Memory MCP Server

      tonyRaafat
      F
      license
      Not graded
      quality
      B
      maintenance
      A remote MCP server that gives Claude (and ChatGPT/Gemini) persistent read/write access to your own memory: books, games, projects, notes, and freeform facts.
      -
    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 4 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: adding, searching, retrieving all, and deleting memories. The descriptions clearly differentiate search from retrieval, so there is no ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (add, search, get, delete + memory/memories). The singular/plural variation is minor and does not hinder predictability.

    Tool Count5/5

    With only 4 tools, the server is well-scoped and focused on the fundamental memory operations. Each tool is essential and there is no bloat.

    Completeness4/5

    The set covers the core lifecycle of memories (create, read, search, delete), but lacks an update operation. This is a minor gap for a memory store, making the surface slightly incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources