ADR Guard

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:

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:

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:

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.