Skip to main content
Glama
elvismdev

mem0-mcp-selfhosted

by elvismdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mem0-mcp-selfhosted

No user-submitted related servers found.

    Related Servers

    • mem0-mcp-selfhosted

      fabiolenine
      A
      license
      A
      quality
      B
      maintenance
      Self-hosted mem0 MCP server for Claude Code that adds durable async ingestion, document support, and reranking, enabling persistent memory management with Qdrant, Neo4j, and Ollama.
      15
      1
      MIT
    • 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-mcp-selfhosted

      jRicci06
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to maintain persistent cross-session memory using self-hosted Qdrant, Neo4j, and Ollama, with optional Anthropic or local LLM backends, and exposes MCP tools for adding, searching, updating, deleting, and graphing memories.
      -

    • mem0-mcp

      andresmorales07
      A
      license
      A
      quality
      C
      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
    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.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct purposes: add, get, update, delete, search, and entity management. However, delete_all_memories and delete_entities could be confused as both are bulk deletions, and get_memories vs search_memories may cause ambiguity despite different filtering/semantic approaches.

    Naming Consistency4/5

    The majority follow a consistent verb_noun pattern (e.g., add_memory, delete_memory). Two tools (mcp_get_entity, mcp_search_graph) deviate with an 'mcp_' prefix, breaking the otherwise uniform style.

    Tool Count5/5

    With 11 tools, the server covers core memory CRUD, search, and entity operations without being excessive. This count is well-scoped for a focused memory management MCP server.

    Completeness5/5

    The tool surface includes creation, retrieval (by ID, pagination, semantic search), update, and multiple deletion methods, plus entity listing and graph search. This provides comprehensive lifecycle coverage for agent memory management.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources