AdrMcp MCP Server

MCP server for Architectural Decision Records: navigate, author, validate, link, and analyze them.

What it actually does

Architectural decisions get made in Slack threads, PR comments, and someone's head — then the reasoning evaporates. Months later a teammate asks "why is it done this way?", nobody remembers, and the decision gets silently re-litigated or accidentally reversed. ADRs fix that — if they're written and kept honest. But a folder of Markdown files is inert: you can't ask it what's still accepted, trace what superseded what, or notice a decision that no longer matches the code.

• Read & search ADRs — — list_adrs, get_adr, search_adrs (lexical or semantic), and get_adr_index for the full decision timeline
• Author from a template — — create_adr drafts MADR- or Nygard-format ADRs; update_adr replaces or appends a single section
• Lifecycle-aware transitions — — set_status enforces the ADR lifecycle; supersede_adr creates the replacement and marks/links the old one superseded in a single call
• Relationship graph & staleness detection — — find_related_adrs / get_adr_graph expose links and supersession chains; find_stale_adrs flags ADRs whose code_refs no longer resolve in the codebase
• Conflict & coverage analysis — — detect_conflicts surfaces contradictory accepted decisions; coverage_report highlights ADR coverage gaps by architectural area
• Preview-by-default writes — — every mutating tool defaults to previewOnly: true and returns a unified diff before anything touches disk

Configuration

• .NET SDK

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.