Skip to main content
Glama

Related Servers

Alternatives to OpenMemory MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives every Claude surface (claude.ai, Desktop, mobile, Office add-ins, Claude Code) read and write access to the memories, transcripts and notes produced by Claude Code instances on all of your machines, with hybrid keyword and semantic search. Runs as a self-hosted remote MCP server with GitHub allowlist authentication, secret redaction and audit logging.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to persistently add, search, update, and delete memories backed by self-hosted Qdrant vector storage, an optional Neo4j knowledge graph, and Ollama embeddings, using either Anthropic or a fully local LLM for fact extraction. It also exposes graph entity tools and session hooks so relevant context is automatically injected at startup and summaries saved on exit.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables personal AI memory management through MCP tools for adding, searching, exporting, and deleting memories, with knowledge-graph retrieval and multi-hop association for clients like Claude Desktop and Cursor.
      6
      1
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude Desktop and compatible agents to search, read, add, update, and delete a locally stored, user-curated memory using hybrid retrieval with reranking and Qdrant. All processing runs locally without cloud services or API keys.
      9
      21 PyPI
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to add, search, update, delete, and organize persistent memories across sessions using self-hosted Qdrant, Neo4j, and Ollama, with optional Anthropic or local LLM support. It also exposes tools for knowledge-graph entity relationship search and retrieval.
      -

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    search_memories and semantic_search are clearly differentiated by keyword vs. meaning-based, though reinforce_memory overlaps with semantic_search's side effect of marking memories as seen and raising salience. The other tools (add, list, get, delete, health_check) are distinct.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (search_memories, add_memory, list_memories, get_memory, delete_memory, reinforce_memory, health_check). health_check is a minor deviation but still clearly named.

    Tool Count5/5

    Eight tools form a well-scoped set for a memory management server, covering search, CRUD, and health checks without bloat.

    Completeness4/5

    Core lifecycle (create, read, list, delete, search) and utility (health_check, reinforce) are covered. Missing an explicit update_memory tool, though the description suggests adding a corrected memory as a workaround.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues