Skip to main content
Glama
adrianczuczka

mason

by adrianczuczka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mason

  • FileScopeMCP

    admica
    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
    -

  • ontomics

    EtienneChollet
    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
    43
    MIT

Related Servers

  • aoci-code

    aoci-spec
    F
    license
    A
    quality
    B
    maintenance
    A persistent, Git-versioned map of your whole codebase and database schema that coding agents read before they touch anything. Local-first MCP server + CLI in Go: a governed repository index of code knowledge that gives Claude Code, Codex, Cursor, and opencode long-term context, memory, and code intelligence.
    9
    1,803
    -

  • codegraph

    mooyee0929
    A
    license
    B
    quality
    C
    maintenance
    Indexes a Python/JS/TS repository into a local SQLite knowledge graph so agents can trace callers, callees, imports, subclasses and covering tests, measure impact radius, rank diff risk, and summarize architecture without grepping files. Exposes these queries as MCP tools alongside an equivalent CLI, with no daemon, embeddings, or network access.
    10
    MIT

  • obsidian-local-mcp

    lasheralberto
    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
    -

  • Prism

    Shailesh200
    A
    license
    Not graded
    quality
    A
    maintenance
    Gives coding agents local software intelligence: it surfaces the files, tests, and helpers relevant to a task before edits, flags missed callers and uncovered code during review, and returns a single SHIP / NOT PROVEN / NO-SHIP verdict when the agent stops. Everything runs on the local index with no network calls, so repository code stays on the machine.
    2,013 npm
    10
    MIT

  • memory-for-ai

    LonelyTraderBay
    A
    license
    Not graded
    quality
    A
    maintenance
    Turns a codebase into a persistent knowledge graph so AI coding agents can answer structural questions about functions, call chains, routes, and cross-service links through graph queries instead of reading files one by one.
    MIT
Deploy Server
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A3.7/5.0

Scored across 12 tools

Disambiguation4/5

Most tools target clearly different resources (context, impact, decisions, verification, automation), and descriptions work hard to separate them. However the snapshot trio (get_snapshot/verify_snapshot/mason_check_drift) and the context family (get_context/get_impact) sit close together and could be misselected without careful reading. Boundaries are mostly clear but require the verbose descriptions to disambiguate.

Naming Consistency3/5

Within the core set there is a readable verb_noun pattern (get_snapshot, save_snapshot, save_decision, review_decision, verify_snapshot). But this is broken by a mason_ prefix on init, complete_init, check_drift, and automation, plus a non-verb name (mason_automation). The mixed prefixed/unprefixed convention is the main inconsistency.

Tool Count4/5

Twelve tools is within a reasonable range for a rich domain (init lifecycle, map get/save, drift, verify/save verification, decision save/review, context, impact, automation). Each appears to earn its place, though get_snapshot/save_snapshot and verify_snapshot/save_verification pairs could be argued as splittable.

Completeness4/5

The surface covers the full lifecycle: initialization, map creation, drift checks, correctness verification, decision capture and review, context assembly, and impact tracing. Minor gaps exist (no direct decision-listing/query tool and map maintenance limited to save_snapshot), but core workflows are covered without dead ends.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources