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
      A
      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

      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

    • 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

    • NFTS Memory MCP

      newforesttech
      F
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted SQLite-backed memory server for Claude that syncs memories across claude.ai, Claude Desktop, and Claude Code via a single MCP server with OAuth.
      -
    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.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