Skip to main content
Glama
fabiolenine

mem0-mcp-selfhosted

by fabiolenine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mem0-mcp-selfhosted

No user-submitted related servers found.

    Related Servers

    • mem0-mcp by tensakulabs

      mem0-mcpofficial

      tensakulabs
      A
      license
      A
      quality
      C
      maintenance
      Self-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.
      6
      4
      MIT

    • mem0-mcp-selfhosted

      Sompong33136
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to run a self-hosted persistent memory server backed by Qdrant, Neo4j, and Ollama, exposing 11 MCP tools for adding, searching, updating, deleting, and organizing memories and knowledge-graph entities. Supports Anthropic or local Ollama LLMs, automatic session hooks, and cross-session memory management.
      -

    • mem0-local-mcp

      sanchezvivi
      A
      license
      Not graded
      quality
      D
      maintenance
      A fully local, self-hosted memory server for MCP clients (Claude Code, Cursor, etc.) that provides persistent memory storage with semantic search, using local embeddings and a local Qdrant vector store.
      MIT

    • 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.
      24 npm
      5
      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 15 tools

    Disambiguation4/5

    Most tools are clearly distinct (add_memory vs get_memory vs delete_memory, etc.). However, delete_entities and delete_all_memories are noted as functionally equivalent in self-hosted mode, causing some overlap. Also, mcp_get_entity and mcp_search_graph could be confused for entity lookups.

    Naming Consistency3/5

    Many tools follow verb_noun pattern (add_memory, get_memory, delete_memory), but some use noun_first (memory_history, memory_queue_status) and two are prefixed with 'mcp_' (mcp_get_entity, mcp_search_graph), breaking consistency. Overall readable but mixed.

    Tool Count5/5

    15 tools is well-scoped for a memory server. It covers CRUD, search, history, async task management, entity operations, and document ingestion without excess.

    Completeness4/5

    Core memory operations are fully covered (add, get, update, delete, search, history). Entity management and async task monitoring are included. Minor gap: no task cancellation tool. Also, delete_entities is redundant with delete_all_memories.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources