Skip to main content
Glama
TimWongUp

keepygaga

by TimWongUp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to keepygaga

No user-submitted related servers found.

    Related Servers

    • aurum-recall

      bryanslongbl-sys
      A
      license
      A
      quality
      B
      maintenance
      A memory system for AI agents that maintains a human-readable, typed Markdown knowledge base with an always-in-context index, enabling recall, correction, and trust decay through MCP.
      7
      1
      Apache 2.0

    • mnemo

      Nas01010101
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to have persistent, self-managing memory with bi-temporal supersession, timely forgetting, and recall under a limited context window, using MCP protocol.
      MIT

    • KOPENG

      djy89
      F
      license
      Not graded
      quality
      B
      maintenance
      Persistent, self-curating memory for coding agents. It enables local, zero-cost context recall through MCP tools with hybrid retrieval and autonomous consolidation.
      -

    • engram

      tanvi-s18
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to store, recall, and manage persistent memory across sessions through MCP tools, with reviewable handoffs and SQLite-backed local storage.
      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

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    The tools are mostly distinct: list and read serve different read purposes, and create/add/update/move/delete each target specific fact or page operations. However, update, move, and delete each have secondary description-related behaviors, so an agent could occasionally hesitate between mutation tools without carefully reading the details.

    Naming Consistency5/5

    All tool names are lowercase single-word imperative verbs: list, read, create, add, update, move, rename, delete. This is a highly consistent and predictable naming convention, with no mixed styles or vague generic names.

    Tool Count5/5

    Eight tools is well within the ideal range for a content-management server covering facts and pages. Each tool occupies a distinct role in the read/create/update/delete lifecycle, and none feel redundant or excessive.

    Completeness4/5

    The surface covers core page and fact lifecycle operations well: read/list, create/add, update/move/rename, and delete. Minor gaps exist, such as no fact-level search or standalone fact listing, but agents can work around these by reading canonical page paths.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources