Skip to main content
Glama

Related Servers

Alternatives to forja

No user-submitted related servers found.

    Related Servers

    • 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
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to keep sessions short by compacting early, saving a handoff and restoring it afterwards, while automatically recalling relevant project knowledge on every request. It exposes a code map ranked with PageRank and a temporal knowledge graph of decisions, bugs, gotchas and concepts, searched with hybrid BM25, Personalized PageRank and Reciprocal Rank Fusion within a token budget.
      5 npm
      13
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to understand unfamiliar codebases through project summaries, file explanations, feature tracing, change planning, test discovery, guided walkthroughs, and token-efficient repository digests.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Persistent, compact project memory for AI coding agents, enabling them to read a small digest instead of re-scanning the codebase every session, saving tokens and costs.
      49 npm
      2
      MIT

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool has a fairly distinct role: learn/recall handle memory (write vs read), check/test/gate handle verification, and fix/mutate/overview/outline are clearly separate operations. The main risk is check vs gate (gate is explicitly 'check + test in one call') and overview vs outline, but the descriptions clarify the boundaries well.

    Naming Consistency4/5

    All nine tools use a single lowercase word with no style mixing, which is highly consistent. It is not a verb_noun pattern and mixes verbs (learn, fix, test, mutate, recall, check) with nouns (overview, outline, gate), but the stylistic convention is uniform and readable.

    Tool Count5/5

    Nine tools is well-scoped for a code QA/testing server, with each tool covering a distinct aspect (memory, static check, tests, combined gate, mutation testing, safe fixes, project mapping, file outline). No obvious redundancy or padding.

    Completeness4/5

    The surface covers a solid lifecycle: explore (overview/outline), verify (check/test/gate), improve (fix), assess test quality (mutate), and accumulate knowledge (learn/recall). Minor gaps exist, such as no way to remove/update a stored lesson, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data