Skip to main content
Glama
kaidewu01

hippocampus

by kaidewu01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hippocampus

No user-submitted related servers found.

    Related Servers

    • litopys by litopys-dev

      litopysofficial

      litopys-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent graph-based memory for AI agents, stored as plain markdown — no vector DB. Typed nodes and 11 relation types via 5 MCP tools (search, get, create, link, related), stdio and HTTP/SSE transports.
      3
      MIT

    • mcp-memory-sqlite

      alexfayers
      A
      license
      Not graded
      quality
      F
      maintenance
      A personal knowledge graph and memory system for AI assistants using SQLite with FTS5 full-text search, enabling persistent memory across conversations with Claude or any MCP-compatible AI.
      2
      MIT

    • synapse

      anshulyadav1976
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI agents with a local, private Markdown-based memory vault and SQLite search. Enables agents to search, read, list, and traverse linked knowledge pages via MCP with zero external runtime dependencies.
      6
      MIT

    • Multi-Agent Memory MCP

      jhunter11
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides local-first persistent memory with a typed knowledge graph and bounded multi-hop retrieval via MCP, letting coding agents and local LLM systems store, search, and recall facts across sessions without hosted services or model dependencies.
      MIT

    • memorry

      macbyclp
      A
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP memory server that stores facts in SQLite with FTS5 full-text search, supports projects and pinned records, and optionally syncs to Obsidian, all without external API calls.
      3
      MIT

    • life-context

      MSIH
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first memory server that stores notes, contacts, and future data as a unified entity graph, providing hybrid retrieval (vector + keyword) for AI assistants via MCP.
      1
      MIT
    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

    B3.2/5.0

    Scored across 21 tools

    Disambiguation4/5

    The three prefixed domains (personal/tech/conversation) are clearly separated, and most tools target a distinct resource or action. Within personal, however, personal_provenance and personal_get_node both expose raw document text, and personal_neighbors/personal_graph both return graph-like views, requiring careful reading of descriptions.

    Naming Consistency4/5

    The personal_/tech_/conversation_ prefixes create clear namespaces, and most tools follow a verb_noun pattern. A few personal_ names are bare nouns (provenance, neighbors, graph) rather than action verbs, which is a minor but noticeable inconsistency.

    Tool Count3/5

    21 tools is on the heavy side for a single MCP server, even though the load is distributed across three distinct modules. The count feels manageable but exceeds the typical well-scoped range.

    Completeness4/5

    Core workflows are well covered: creating and linking entities, adding documents/attachments, searching and retrieving content, updating tech observations, and importing/auditing conversations. The main gaps are the lack of a general delete/detach operation and limited batch listing, but these can usually be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources