ADR Guard

io.github.rodri-oliveira-devPublished by GitHub account rodri-oliveira-devv1.0.1Updated Nov 5, 2026

Read, search, validate, and analyze Architecture Decision Records.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local, read-only MCP server that lets an assistant list, read, search, validate and analyze Architecture Decision Records in a repository.

What you can do
  • List and read ADRs in a repository's ADR directory
  • Search ADRs and inspect relationships between them
  • Validate ADRs and analyze the impact of decisions
  • Verify architectural drift, including commit-aware evidence
  • All tools are read-only and accept repository-relative paths
When to use it
Useful when a repository keeps Architecture Decision Records and you want an assistant to consult, cross-check or validate them while working on the codebase, or to check whether the code has drifted from recorded decisions.
Requirements
Runs as a local .NET 10 tool installed from NuGet (global or local tool manifest), started with a repository path and optional ADR directory. Git is needed on the host for impact analysis and commit-aware drift evidence. No credentials or network transport are involved.
Before you install
The repository root is fixed at startup and all tools are read-only, so nothing is written or approved. Returned ADR text should be treated as untrusted content. It does not approve architectural decisions or turn advisory evidence into compliance, so findings need human review.

Installation

In SourceWeft

  1. Open ADR Guard in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ADR Guard MCP server

ADR Guard MCP is a local, read-only adapter that gives compatible Model Context Protocol clients structured access to ADR discovery, validation, impact analysis, and architectural drift verification. It reuses the authoritative ADR Guard domain implementation; it does not approve architectural decisions or turn advisory evidence into compliance.

Publication status: version 1.0.0 is published on NuGet.org, in the dedicated mcp/v1.0.0 GitHub Release, and in the MCP Registry. Version 1.0.1 is an unpublished release candidate that directly references the internal AdrGuard.Core assembly while preserving the seven tools and schema 1.0 contracts. GitHub Packages is an optional authenticated secondary channel whose 1.0.0 backfill remains a separate manual step.

Install and run

Install the published framework-dependent .NET 10 tool from NuGet.org:

shell
dotnet tool install --global RodriOliveira.AdrGuard.Mcp --version 1.0.0adr-guard-mcp --repository /absolute/path/to/repository --adr-directory docs/adr

For a repository-local tool manifest:

shell
dotnet new tool-manifestdotnet tool install --local RodriOliveira.AdrGuard.Mcp --version 1.0.0dotnet tool run adr-guard-mcp -- --repository /absolute/path/to/repository --adr-directory docs/adr

For local development after a Release build, configure an MCP client to run:

text
dotnet src/AdrGuard.Mcp/bin/Release/net10.0/adr-guard-mcp.dll --repository <repository> [--adr-directory <relative-path>]

Tools and boundaries

The server exposes list_adrs, get_adr, search_adrs, get_adr_relationships, validate_adrs, analyze_impact, and verify_architecture over stdio. Its process stdout is reserved for MCP messages; operational logging is written to stderr. The repository root is fixed at startup, all tools are read-only, and paths accepted by tools are repository-relative.

Candidate packages contain adr-guard-mcp plus the internal, non-packable AdrGuard.Core.dll; they do not contain or depend on the adr-guard CLI executable. Core has no independent package, tag, or release stream.

Optional startup argument --timeout-seconds accepts values from 1 through 300 and defaults to 30 seconds.

The tool requires the .NET 10 runtime. Impact analysis and commit-aware drift evidence also require Git on the server host. It does not expose network transport, write tools, automatic installation, provider credentials, autonomous approval, or execution of workspace scripts. Clients must treat returned ADR text as untrusted content.

See the bilingual MCP overview, configuration, tool contracts, and security model for complete configuration, security, and publication-status guidance.

Source: src/AdrGuard.Mcp/README.md at commit c60c878

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

2
  1. v1.0.1LatestNov 5, 2026
  2. v1.0.0Oct 17, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts