briefd
Related Servers
Alternatives to briefd
- AlicenseAqualityAmaintenanceA local MCP server that gives AI assistants persistent long-term memory using a biological neural architecture with cortex, synapses, and hippocampus.8151,356 npm7MIT
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for Agent Context OS that compiles engineering docs into a knowledge graph, detects code drift, and serves token-budgeted context packs to AI coding agents via MCP.-
- AlicenseNot gradedqualityDmaintenancePersistent codebase knowledge layer for AI agents. Pre-digests codebases into structured knowledge (symbols, dependency graphs, co-change patterns, architectural decisions) and serves via MCP. 28 languages, 14 tools, ~85% token reduction.11 npm8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to locally search, query, and understand codebases with token-efficient context, dependency graphs, history, architecture diagrams, and metrics through MCP.15 npm3MIT
- AlicenseAqualityAmaintenanceSelf-hosted memory and governance layer for AI coding agents. 28 MCP tools with hybrid search, structured knowledge capture, behavioral nudges, and git-native storage. Zero cloud dependencies.306Business Source 1.1
- AlicenseNot gradedqualityAmaintenanceSelf-hosted AI Agent Memory + Code Intelligence Platform providing persistent memory, AST-aware code search, and quality enforcement via a single MCP endpoint.59MIT
- AlicenseBqualityAmaintenanceEnables AI coding agents to maintain persistent project context, including rules, decisions, environment intelligence, and Git history, using a local-first MCP server with automatic project detection and token-efficient retrieval.13MIT
TDQS
Scored across 7 tools
Most tools are clearly distinct: get_document for full documents by path, list_scopes for discovery, propose_update for writing, suggest_links for maintenance, and report_usage for feedback. The only real overlap is between search_context and compile_bundle, which both return relevant sections with token budgets, though their descriptions give different intended use cases (lookup vs. task compilation).
All seven tools follow a consistent verb_noun snake_case pattern: get_document, compile_bundle, list_scopes, search_context, suggest_links, propose_update, report_usage. Every name clearly pairs an action with an object, and there are no mixed conventions or vague generic verbs.
Seven tools is a well-scoped set for a team knowledge-base server: discovery, retrieval, search, compilation, writing, link maintenance, and usage feedback each have exactly one dedicated tool. The count feels complete without redundancy or bloat.
The surface covers the main lifecycle well: read via get_document/search_context/compile_bundle, update via propose_update, discover scopes via list_scopes, and maintain quality via suggest_links and report_usage. Minor gaps remain—there is no direct way to list all documents in a scope beyond counts, and propose_update doesn't obviously support deletion.