Skip to main content
Glama
hermind-mcp

hermind-mcp

by fungane

Related Servers

Alternatives to hermind-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents a local-first, persistent memory backed by a single SQLite file, letting them save decisions, preferences, and facts, then recall them by meaning or keyword across sessions and projects. Exposes tools for loading pinned context, searching, adding, updating, listing, and deleting memories, so agents stop forgetting between sessions.
      14 npm
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to store, search, and manage persistent memories, todos, kanban boards, reminders, and progress trackers in a local SQLite database.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI coding agents persistent memory by storing observations, decisions, and learnings in a local SQLite database with vector search, full-text search, and a rules engine.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to save, recall, and forget persistent memories stored entirely on the local machine in SQLite, using hybrid semantic and keyword search with on-device embeddings, plus spaces and profile context injection.
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides persistent local memory functionality for AI assistants, enabling them to store, retrieve, and search contextual information across conversations with SQLite-based full-text search. All data stays private on your machine while dramatically improving context retention and personalized assistance.
      3
      -
    • A
      license
      A
      quality
      B
      maintenance
      Gives AI agents persistent, local-first memory using SQLite and on-device embeddings, enabling semantic search and recall across sessions with no cloud calls.
      8
      9
      MIT

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct retrieval axis: query-based search, id-based get, recency-based list, and entity-based related. The only mild overlap is memory_search vs memory_list, both returning notes, but descriptions make the search-vs-browse distinction clear enough.

    Naming Consistency5/5

    All four tools share a single memory_ prefix with a clear verb/noun suffix (search, get, list, related). Predictable and easy to pattern-match.

    Tool Count4/5

    Four read-only tools is a tight, well-scoped set for a memory retrieval server with no redundant entries. It sits at the thin end of the comfortable range, but each tool earns its place.

    Completeness3/5

    The read surface is good (search, fetch, browse, related), but there is no tool to create, update, or delete notes, nor to enumerate available kinds, so agents cannot write to memory through this server. Assuming notes are saved elsewhere this is workable, but it is a notable gap for a memory domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues