Skip to main content
Glama

Related Servers

Alternatives to afr

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that retrieves git-backed engineering experience records (issues, fixes) to inform LLM coding agents, preventing repeated mistakes with a relevance floor.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server enabling AI agents to record, query, and share structured problem-solving experiences with human review and confidence decay.
      2 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      This MCP server enables coding agents to retrieve code across the whole machine through task briefings, exact file and line locations, grounded answers, dependency lookups, session guidance, and status checks, while reporting corrections and knowledge gaps to a separate retrieval engine.
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that gives coding agents persistent, verified memory of codebase decisions, conventions, and skills, with evidence-based claims that are re-checked via git hooks and human-gated review. Enables memory search, propose/approve, chat harvesting, and critique across MCP-compatible tools.
      21
      112 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A local MCP server that lets coding agents persist decisions, conventions and gotchas across sessions and recall them with ranked search. Each memory is anchored to the files it describes, so recall flags it as stale when that code changes, and secrets are redacted before anything is stored.
      5
      2
      MIT

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: search retrieves experiences, get_episode_evidence fetches evidence by episode id, and report_task_outcome records an outcome. The descriptions make the read/search/write boundaries explicit, so an agent can reliably select the right tool.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: search_experience, get_episode_evidence, report_task_outcome. There are no mixed conventions or vague names.

    Tool Count5/5

    Three tools is appropriately minimal for this focused experience-retrieval and reporting server. Each tool serves a distinct, necessary function without redundant operations.

    Completeness3/5

    The set covers searching experiences, retrieving evidence, and reporting outcomes, but lacks any explicit way to create or record new episodes/lessons or add verification evidence. Those omissions are notable for a system centered on recorded experience, even if ingestion may happen outside the MCP surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues