Skip to main content
Glama

Related Servers

Alternatives to briefd

  • A
    license
    A
    quality
    B
    maintenance
    A local MCP server that gives AI assistants persistent long-term memory using a biological neural architecture with cortex, synapses, and hippocampus.
    15
    777 npm
    8
    MIT

Related Servers

  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP 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.
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    Persistent 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 npm
    10
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Self-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.
    30
    6
    Business Source 1.1
  • A
    license
    Not graded
    quality
    B
    maintenance
    Self-hosted AI Agent Memory + Code Intelligence Platform providing persistent memory, AST-aware code search, and quality enforcement via a single MCP endpoint.
    105
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    Enables 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.
    13
    MIT

TDQS

A4.6/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityNo data
ResponsivenessOutdated data