Skip to main content
Glama

Related Servers

Alternatives to obituary

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to record rejected approaches, decisions, and constraints, with expiring reasons, in a git-tracked Markdown store the agent consults before proposing anything. This makes agents stop re-suggesting options that were already ruled out, and entries quietly drop out of view once they lapse.
      15 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to carry durable project memory across windows, agents, and days, injecting a compressed context of architecture, progress, decisions, and critical files so a new session can resume without re-reading the whole repository. It also classifies files as current/legacy/intermediate and suggests cleanup so stale or draft artifacts don't mislead the agent.
      8 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Long-term memory for AI coding agents, stored as a tree of plain local files. Agents search it before answering and save what lasts; changed facts are kept as history and flagged as outdated.
      9
      124 PyPI
      38
      MIT

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool maps to a distinct lifecycle action: mark registers, extend adjusts lifespan, bury moves to graveyard, resurrect restores, and spare stops tracking. The three listing tools (list, graveyard, proposals) share similar pagination semantics but target different collections, so confusion is limited.

    Naming Consistency4/5

    All tools share the obit_ prefix and snake_case formatting, which is highly predictable. However, some names are nouns (graveyard, proposals, stats) while others are verbs (bury, extend, mark), so the verb_noun pattern is not perfectly uniform.

    Tool Count5/5

    Ten tools is a well-scoped size for a file lifespan and graveyard management server. Each tool appears to earn its place by covering a specific lifecycle operation without obvious redundancy.

    Completeness4/5

    The surface covers registration, listing, extension, untracking, burial, restoration, graveyard viewing, temp creation, proposals visibility, and stats. Permanent purging and proposal approval are intentionally left to the user/CLI, so the main lifecycle is complete with only minor intentional gaps.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data