Mason
MCP serverDocs & knowledgeEngineering decisions, change impact, documentation audits, and CI evidence for coding assistants.
Unavailable. This server has no hosted endpoint yet, so ahel can't serve it.
Connect ahel once, and every AI you use reads what you have installed.
From the project's README
As published by adrianczuczka/mason in README.md.
Your agents are creating tech debt. Mason helps you prevent it.
Remember why decisions were made · Catch outdated guidance · Find what else needs updating
Get started
Install on macOS or Linux:
curl -fsSL https://github.com/adrianczuczka/mason/releases/latest/download/install.sh | sh
Windows PowerShell:
irm https://github.com/adrianczuczka/mason/releases/latest/download/install.ps1 | iex
No Node or npm required. Git is required. The installer configures PATH for Bash, Zsh, and Windows. Platform details · npm installation
Run this in your Git repository (open a new terminal if the installer asks):
mason setup --host codex
# For Claude Code, use --host claude.
Setup connects MCP, hooks, and project instructions. Review your host's trust settings, start a new session, and give your agent a normal task.
Check that Mason is being used:
mason status
Setup uses your installed mason command—no project launch scripts or runtime copies. Status distinguishes configuration from observed use. Setup and upgrades · Disconnect a project · Other MCP clients
Try a check without setup
mason audit --dir .
mason review --dir . --base origin/main
The audit checks claims in README and agent instruction files throughout the repository. The review checks committed changes against your chosen base. Both are read-only and need no model calls.
What Mason catches
| As your project grows… | Mason helps by… |
|---|---|
| Instructions fall behind the code. | Flagging missing paths, incorrect workspace counts, and missing npm scripts. |
| A patch misses a related update. | Surfacing references, related tests, and files that historically change together. |
| Old decisions lose their context. | Retrieving recorded rationale and review status, and flagging changes to the code they apply to. |
| A repair gets interrupted. | Retaining the original findings and verifying them through the final documentation commit. |
After resolving an incident or settling a constraint, ask your agent to record the reason with Mason. Later tasks can retrieve it. Proposals and accepted decisions stay distinct.
Mason complements tests, linters, and code review. Findings are evidence to inspect; unavailable checks stay explicit.
Evidence so far
Earlier read-only decision-retrieval evaluations scored 9.0/10 with Mason vs 7.0/10 without. The initial ten-task patch comparison tied at 10/10 for both. Improved patch outcomes remain to be demonstrated. Results, methodology, and limitations
Documentation
Tools it gives your AI (18)
| Tool | What it does |
|---|---|
| mason_init | Start here. Checks if Mason is set up for this project. If not, returns a `playbook` of questions the assistant must walk the user through (concept map + optional Confluence sync). |
| mason_complete_init | Mark the project as initialized. Call this after walking the user through the playbook returned by `mason_init`. Writes `.mason/project.json` so future tool calls don't re-run the wizard. |
| mason_set_confluence | Configure Confluence credentials. Two-step flow: (1) call without `spaceKey` to validate the credentials and receive a list of available spaces — relay them to the user. |
| full_analysis | One-shot orientation for a project WITHOUT a concept map (get_snapshot returned exists:false). |
| analyze_project | Run git history analysis on a codebase. Returns commit convention patterns, stale directories, and frequently changed files. |
| get_code_samples | Get previews (first ~60 lines) of representative source files from the codebase. Includes entry points, config files, hot files (frequently changed), test examples, and one file per directory for... |
| get_snapshot | CALL THIS FIRST — before grep, glob, or reading files — for any question about what this codebase does, its features, architecture, data flows, or where something is implemented ('where is X... |
| get_context | CALL THIS FIRST when given a task to implement, a bug to fix, a ticket, or a change request ('add X', 'fix Y', 'refactor Z'). |
| generate_snapshot_batch | Map step of the concept-map build. Returns one batch of source files (skeletons of every file in the batch plus a few deeper-read bodies for grounding), along with a system prompt instructing you to... |
| save_partial_snapshot | Persist the partial concept map you derived for one batch. Call this once per batch, with the `batchId` from the `generate_snapshot_batch` response. |
| reduce_snapshot | Reduce step of the concept-map build. Returns every partial snapshot plus a system prompt asking you to merge them into one coherent project-wide map. |
| save_snapshot | Save a concept-to-files map as a persistent project snapshot. Maps feature names and data flows to the files that implement them. |
| save_decision | CALL THIS when you learn something about this codebase that the code alone can't tell you: a failed approach ('we tried X, it broke Y'), a deprecation ('don't extend Z'), a workaround and its... |
| mason_check_drift | Check how far the concept map has drifted from HEAD. Deterministic (git + filesystem, no LLM). |
| verify_snapshot | Spot-check the concept map's CORRECTNESS (drift checks freshness; this checks entries were right to begin with). |
| save_verification | Record verify_snapshot verdicts. Entries judged ok are stamped verifiedAt; failures are flagged verificationFailed with your note and surface in mason_check_drift until re-mapped. |
| get_impact | CALL THIS BEFORE editing, refactoring, or assessing the blast radius of any file. Returns three signals you cannot get by reading the file itself: git co-change history (files that historically... |
| export_to_confluence | Sync the project's concept map to Confluence as product-readable wiki pages: an index page, one page per feature (PM-language descriptions, no file paths), and a changelog page. Hand-edits outside `<! |
Signals
- Tools captured
- 18
Advanced
- Delivery
- mason MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
- Catalog kind
- mcp-server
- Gateway key
com-adrianczuczka-mason- Source
- github.com/adrianczuczka/mason