Skip to main content
Glama
dafarusd

keephaven-mcp

by dafarusd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to keephaven-mcp

No user-submitted related servers found.

    Related Servers

    • fimemory by FutureAiIndustries

      fimemoryofficial

      FutureAiIndustries
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to read and write a local, encrypted-by-default memory store, so they can share persistent notes and context across sessions and models on your machine.
      38 npm
      -

    • iifa

      Balidriss
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to remember people, projects, places, and topics across conversations under a strict token budget, returning compact handles with expandable details while preserving changes, provenance, and encrypted self-hosted storage.
      Apache 2.0
    • Qoopia by qoopia

      Qoopiaofficial

      qoopia
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent memory for AI agents via MCP, enabling agents to store and access notes, files, and session context across sessions and clients while under user control.
      4
      MIT

    • MemoryAI

      toozuuu
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to automatically capture durable knowledge and retrieve only relevant, token-bounded context from a secure local-first long-term memory, with support for progressive disclosure, snapshots, health diagnostics, and background tasks.
      Apache 2.0
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair: memory file operations, append-only journal operations, search, and status. The boundary between memory_write and journal_append is explicitly clarified, preventing likely misselection.

    Naming Consistency5/5

    All tools follow a predictable resource_action pattern: memory_* for file memory and journal_* for journal operations. The convention is consistent and easy to infer.

    Tool Count5/5

    Eight tools are well-scoped for a memory/filesystem server with an append-only journal. Each tool has a clear role without excessive fragmentation.

    Completeness5/5

    The set covers memory file CRUD (read/write/list/delete), identity and quota status, search across memory and journal, and append/read journal lifecycle. The append-only journal intentionally omits edit/delete operations, so the surface is complete for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources