Skip to main content
Glama

Related Servers

Alternatives to Alethea

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to record, search, and supersede ADR-style decisions and machine-checkable constraints stored as git-friendly markdown in a repository, linked to SpecGate requirement ids, tests and commits. It also surfaces the relevant constraints and decisions for a task and checks a proposed change or diff for conflicts before it is committed.
      7
      347 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and manage a Git-native decision ledger, providing tools for querying decisions, evidence, cross-repository workspaces, validation, and commit tracing, all operating locally and without a cloud service.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      The decision system for agentic engineering: keeps your project's decisions, rationale, and rejected paths in plain files and surfaces them to AI coding agents before they plan or change code.
      11
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI coding agents persistent, branch-aware memory and a dependency-tracked task graph by storing decisions, lessons, and tasks as plain JSON and Markdown committed directly into the repository. Agents can record and fuzzy-search past decisions, dump instant project context, and create, claim, complete, and query tasks whose completion automatically unblocks downstream work.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to persist project memory across sessions by compiling decisions, progress, and pitfalls into git-linked, evidence-backed entries. It lets clients add, query, inject, scan for stale, check assertions on, and compute ROI of those memories over stdio.
      367 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct operation: record (write), supersede (replace), link (associate), check_conflicts (validate), plus several read paths. The read tools (search_decisions, list_constraints, get_context_for_task) overlap somewhat in retrieval purpose, but descriptions clarify their distinct scopes (BM25 search vs. constraint listing vs. task-oriented context assembly).

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (record_decision, search_decisions, get_context_for_task, list_constraints, check_conflicts, supersede_decision, link_requirement). No mixing of conventions or vague verbless names.

    Tool Count5/5

    Seven tools is well-scoped for an ADR/constraint management server, with each tool covering a genuine part of the decision lifecycle (capture, retrieve, validate, supersede, link). No redundant or filler tools.

    Completeness4/5

    Core lifecycle is well covered: record, search, list, supersede, conflict-check, and requirement linking. Minor gaps exist — there is no tool to change a decision's status (accept/reject/deprecate) without superseding it, and no delete/archive path — but supersede and record largely cover practical workflows.