Skip to main content
Glama
andresmorales07

mem0-mcp

by andresmorales07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mem0-mcp

No user-submitted related servers found.

    Related Servers

    • mem0-custom-mcp

      emasoudy
      A
      license
      A
      quality
      D
      maintenance
      A custom MCP server that connects to self-hosted Mem0 API instances, enabling Claude Code to manage memories via custom endpoints.
      4
      1
      MIT

    • zime-memory

      zime78
      F
      license
      Not graded
      quality
      D
      maintenance
      A personal memory MCP server for Claude Code that stores and retrieves memories via natural language, supporting text, images, files, and secrets with vector search.
      -

    • claude-memory

      NathanNorman
      A
      license
      Not graded
      quality
      C
      maintenance
      A persistent memory MCP server for Claude Code that enables long-term recall across sessions via hybrid search, code intelligence, and tools for reading/writing memory.
      5
      1
      MIT

    • recall

      Zavelinski
      A
      license
      A
      quality
      C
      maintenance
      A zero-dependency MCP server for cross-session memory recall in Claude Code. Provides lexical search, listing, and retrieval of past session memories to avoid re-explaining context.
      3
      16
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list, get, add, search, update, and delete memories. There is no functional overlap; even get vs list are differentiated by retrieval method (by ID vs. enumeration).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_, get_, add_, search_, update_, delete_). Minor singular/plural variation (memory vs memories) is natural and does not affect predictability.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a memory management system. Each tool covers a necessary operation without redundancy or bloat.

    Completeness5/5

    The tool set provides full CRUD coverage (add, get, update, delete) plus list and semantic search. There are no missing lifecycle operations for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources