afr
Related Servers
Alternatives to afr
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA 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
- AlicenseNot gradedqualityDmaintenanceAn MCP server enabling AI agents to record, query, and share structured problem-solving experiences with human review and confidence decay.2 npmMIT
- AlicenseAqualityCmaintenanceThis 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.10MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for a shared Postgres-backed knowledge base with hybrid retrieval and agentic RAG, enabling coding agents to upload, search, and ask questions over documents with cited answers.-
- AlicenseAqualityBmaintenanceMCP 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.21112 npm1MIT
- AlicenseAqualityBmaintenanceA 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.52MIT
TDQS
Scored across 3 tools
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.
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.
Three tools is appropriately minimal for this focused experience-retrieval and reporting server. Each tool serves a distinct, necessary function without redundant operations.
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.