Skip to main content
Glama
hrmtz

hippocampus-mcp

by hrmtz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hippocampus-mcp

No user-submitted related servers found.

    Related Servers

    • ilma

      Brotal-LLC
      A
      license
      Not graded
      quality
      A
      maintenance
      Framework-agnostic MCP server for agent memory with Postgres + pgvector, enabling persistent memory, recall, and task management across sessions.
      MIT

    • mesh-memory

      dklymentiev
      A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted semantic memory for AI agents. Save worklogs, decisions, and notes via MCP, then recall them across sessions by meaning rather than keyword. Backed by Postgres + pgvector with local embeddings (multilingual-e5-base).
      1
      MIT

    • tartarus-mcp

      saluca-labs
      A
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP memory server providing persistent, searchable memory for AI agents, powered by SQLite.
      1 npm
      1
      Apache 2.0

    • agenticmemory

      jyswee
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory MCP server for AI agents that stores, recalls, and searches conversation history, key-value context, and long-term entries across sessions with semantic search and FIFO queues.
      48 npm
      1
      -

    • brain-mcp

      markschaake
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides persistent semantic memory backed by PostgreSQL and pgvector for storing and searching thoughts via vector embeddings. It enables dimensional organization, conflict detection, and historical tracking of facts, decisions, and observations.
      9 npm
      AGPL 3.0
    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

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of memory retrieval: full conversation, summary, diary, project-scoped conversations, recent conversations, and ghost memories. No overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent 'verb_noun' pattern with underscores: get_conversation, get_conversation_summary, get_diary, list_project_conversations, list_recent_conversations, search_ghost_memory. Verbs are indicative of the operation.

    Tool Count5/5

    With 6 tools, the server covers the core memory retrieval operations without being bloated. Each tool serves a clear need within the domain of personal memory access.

    Completeness4/5

    The tool set provides multiple ways to retrieve conversations, diary entries, and ghost memories. A minor gap is the lack of semantic search across conversations themselves, but the existing tools cover primary use cases.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources