Architecture Drift MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARCH_DRIFT_ALLOWED_ROOTS | Yes | A list of allowed project root directories that the MCP server can access. Must be set to the paths you want the server to examine. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_auditC | Create a bounded audit and persist its redacted architecture objective. |
| list_auditsA | List persisted audits without reading their project trees. |
| get_auditB | Return the current source, claim, fact, comparison, and proposal snapshot. |
| discover_sourcesB | Refresh the bounded project inventory and invalidate derived stale records. |
| extract_claimsA | Extract claims and reject every host claim without a valid line citation. |
| extract_factsA | Extract current implementation facts from discovered non-documentation files. |
| compare_driftC | Compare normalized claims and facts; absence remains suspected or unknown. |
| adjudicate_driftB | Ask the host model to adjudicate drift using only cited, known claim and fact IDs. |
| propose_doc_patchesA | Generate cited review-only document replacements without writing project files. |
| build_drift_reportA | Write a redacted Markdown and JSON report in the external audit state directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit_prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct responsibility, from audit lifecycle (create/list/get) to the analysis pipeline (discover/extract/compare/adjudicate) to output generation (propose/build). No two tools appear to perform overlapping actions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case, with specific verbs like create, list, get, discover, extract, compare, adjudicate, propose, and build. There is no mixing of conventions or ambiguous verbs.
Ten tools is within the optimal range for a specialized workflow. Each tool contributes a unique step in the architecture drift detection process without redundancy or unnecessary bloat.
The tool set covers the full drift detection workflow: audit creation, source discovery, claim/fact extraction, comparison, adjudication, patch proposal, and report generation. Minor gaps exist such as no explicit audit deletion or patch application, but these are not core to the domain.