briefd
Related Servers
Alternatives to briefd
- AlicenseAqualityBmaintenanceA local MCP server that gives AI assistants persistent long-term memory using a biological neural architecture with cortex, synapses, and hippocampus.15777 npm8MIT
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.22 npm10MIT
- 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
- AlicenseAqualityBmaintenanceSelf-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 gradedqualityBmaintenanceSelf-hosted AI Agent Memory + Code Intelligence Platform providing persistent memory, AST-aware code search, and quality enforcement via a single MCP endpoint.105MIT
- AlicenseBqualityCmaintenanceEnables 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
Each tool has a clearly distinct role: discovery (list_scopes), lookup (search_context), full read (get_document), task-scoped context (compile_bundle), write (propose_update), hygiene (suggest_links) and feedback (report_usage). The only potentially adjacent pair, search_context vs compile_bundle, is explicitly separated as 'look something up' versus 'one context block for a task', and descriptions reinforce each other.
All seven names follow a consistent snake_case verb_noun pattern (report_usage, get_document, propose_update, compile_bundle, list_scopes, search_context, suggest_links). Verbs are distinct and meaningful, with no camelCase or noun-only outliers.
Seven tools is well-scoped for a knowledge-base server, covering the read/discover/write/feedback lifecycle without redundancy. Each tool earns its place and none feels like filler.
The surface covers the core lifecycle: scope discovery, search, full document read, bundle compilation, proposed edits/creation, link cleanup, and usage feedback. Minor gaps remain: no way to delete or archive a document, and no explicit list/browse of documents within a scope (only counts), so agents must go through search to enumerate content.