Skip to main content
Glama

Related Servers

Alternatives to mason

  • F
    license
    A
    quality
    D
    maintenance
    A TypeScript tool that ranks files in your codebase by importance, tracks dependencies, and provides file summaries to help understand code structure through Cursor's Model Context Protocol.
    14
    302
    -
  • A
    license
    A
    quality
    C
    maintenance
    Extract domain knowledge from codebases to reduce LLM token consumption by 20x and time in agentic search by 10x — gathers and makes concepts, naming conventions, and vocabulary queryable via MCP.
    19
    41
    MIT

Related Servers

  • F
    license
    B
    quality
    B
    maintenance
    Turns local code repositories into a queryable dependency graph built from AST parsing and git co-edit history, then exposes it alongside an Obsidian vault as persistent memory. Enables context retrieval, impact analysis of proposed changes, and curation of durable prose knowledge through full-text search and Personalized PageRank classification—all fully offline without API keys or embeddings.
    30
    -
  • 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.
    13 npm
    8
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Turn any codebase into an AI-readable neural map — with proof. Every claim linked to code anchors (line + SHA-256 hash), every context window optimized with greedy token budgeting, every session protected by drift detection. Tree-sitter indexing across 11 languages, cross-session learning, AI enrichment, and 28 MCP tools. Zero config — just connect and your AI agent remembers everything.
    9 npm
    13
    GPL 3.0

TDQS

A3.6/5.0

Scored across 22 tools

Disambiguation3/5

Several tools have overlapping purposes that descriptions only partially resolve: full_analysis vs get_snapshot vs analyze_project vs get_code_samples all return project structure/samples; mason_init vs mason_complete_init vs mason_set_confluence all concern setup; and mason_automation vs mason_repair both touch documentation-repair evidence. The decision/review and map-build/verify pairs are reasonably distinguished, but the boundaries require careful reading.

Naming Consistency3/5

The underlying verb_noun snake_case convention (get_, save_, review_, verify_, export_) is mostly consistent, but roughly a third of tools carry an unexplained `mason_` prefix (mason_init, mason_repair, mason_check_drift) while siblings like get_snapshot and save_decision do not. The prefix usage is arbitrary rather than domain-driven, muddying predictability.

Tool Count3/5

At 22 tools this sits in the heavy zone, though the surface legitimately spans distinct workflows (Map-Reduce map building, verification, drift, decisions, repairs, Confluence export). Multiple setup/repair/analysis tools could likely be consolidated, so it reads as slightly over-scoped rather than tightly scoped.

Completeness4/5

Coverage of the code-analysis/concept-map/decision domain is broad: build, save, verify, drift-check, context assembly, impact tracing, decision capture and review, repair tracking, and Confluence export are all present. Minor gaps remain (e.g. no direct map-entry delete or decision supersede beyond retire), but core lifecycles are covered.

Maintenance

ActivityMaintained
ResponsivenessSlow