Prepare the server locally
Run this once before adding it to Claude Code.
git clone https://github.com/wooxogh/adr-mcp-setup.git
cd adr-mcp-setup
npm installAdd it to Claude Code
Paste the maintainer's config below, then edit any placeholder values.
{
"hooks": {
"Stop": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "node /absolute/path/to/adr-mcp-setup/hook.js"
}
]
}
]
}
}See the adr-mcp-setup README for full setup instructions.
Make your agent remember this setup
adr-skills's config, env vars, and the gotchas you hit — recalled in every future Claude Code, Cursor, and Codex session.
npx conare@latestFree · one command · indexes the sessions already on disk. Set up in the browser instead →
What it does
- Auto-capture of development conversations on Claude Code exit
- AI-powered ADR generation using Claude Opus
- Automated quality scoring and improvement suggestions
- Duplicate detection and dependency graph visualization
- Lifecycle management for ADR status transitions
Tools 9
save_sessionSave a conversation to the databasegenerate_adrAuto-generate an ADR from a sessionreview_adrScore ADR quality and get improvement suggestionsupdate_adr_statusTransition ADR through its lifecyclelink_adrsCreate relationships between ADRsget_adr_graphVisualize the ADR dependency graphcheck_stale_adrsFind old Accepted ADRs that need revisitingsearch_decisionsKeyword search across all past decisionsget_timelineDecision history for a projectEnvironment Variables
ANTHROPIC_API_KEYAPI key for Claude Opus to enable AI-powered ADR generation and quality reviewTry it
Original README from wooxogh/adr-mcp-setup
adr-skills
adr-skills is an MCP server for Claude Code that automatically captures development conversations and uses Claude Opus to generate, review, and manage Architecture Decision Records (ADRs).
TL;DR: Install once, and every Claude Code session ends with a structured ADR saved to
~/.adr-mcp/adrs/— no manual writing required.
What problem does this solve?
Engineering teams make dozens of architectural decisions every week — which database to use, how to handle auth, whether to go monolith or microservices — but rarely write them down. Months later, nobody remembers why Redis was chosen over Memcached, or why the team avoided GraphQL.
adr-skills solves this by turning your existing Claude Code conversations into permanent, searchable ADR documents automatically.
How it works
- You have a normal development conversation in Claude Code
- When the session ends, the Stop Hook captures the transcript
- Claude Opus analyzes the conversation and extracts the architectural decision
- A structured markdown ADR is saved to
~/.adr-mcp/adrs/ADR-0001-*.md - Use
review_adrto score quality,link_adrsto map dependencies,check_stale_adrsto surface outdated decisions
Features
- Auto session capture — Stop Hook saves conversations automatically on Claude Code exit; no manual steps
- AI-powered ADR generation — Claude Opus extracts context, decision, and consequences from raw conversation
- AI quality review — Scores ADR completeness 0–100 and flags missing context, unconsidered alternatives, or optimistic consequences
- Duplicate detection — Warns when a new decision overlaps with a past one before saving
- Markdown export — Every ADR exported as
ADR-NNNN-slug.md, ready to commit alongside your code - Status lifecycle — Track decisions through
Proposed → Accepted → Deprecated → Superseded - Dependency graph — Link ADRs with
related_to,conflicts_with,depends_onand visualize relationships - Stale ADR alerts — Surface
Accepteddecisions older than N months that may need revisiting - Keyword search — Find past decisions by technology name (e.g. Redis, JWT, PostgreSQL)
- Timeline view — Full decision history per project, correlated with git commits
How is this different from existing ADR tools?
| Tool | Auto-capture from chat | AI generation | Quality review | MCP server |
|---|---|---|---|---|
| adr-skills | ✅ | ✅ Claude Opus | ✅ | ✅ |
| adr-tools (CLI) | ❌ | ❌ | ❌ | ❌ |
| mcp-adr-analysis-server | ❌ | ✅ OpenRouter | ❌ | ✅ |
| claude-historian-mcp | ✅ | ❌ | ❌ | ✅ |
| log4brains | ❌ | ❌ | ❌ | ❌ |
No existing tool combines automatic conversation capture with AI-powered ADR generation in a single MCP server. There is an open feature request on the Anthropic repo for native ADR support — adr-skills fills that gap today.
Installation
git clone https://github.com/wooxogh/adr-mcp-setup.git
cd adr-mcp-setup
npm install
Register with Claude Code
claude mcp add adr-skills node /absolute/path/to/adr-mcp-setup/index.js
Environment setup
cp .env.example .env
# Add your ANTHROPIC_API_KEY to .env
Without the API key,
generate_adrfalls back to keyword-based extraction andreview_adris unavailable..envis in.gitignore— your key will never be committed.
Enable auto session capture (Stop Hook)
Add to ~/.claude/settings.json:
{
"hooks": {
"Stop": [{
"matcher": "",
"hooks": [{
"type": "command",
"command": "node /absolute/path/to/adr-mcp-setup/hook.js"
}]
}]
}
}
Tools (9 total)
| Tool | Description | Requires API key |
|---|---|---|
save_session |
Save a conversation to the database | ❌ |
generate_adr |
Auto-generate an ADR from a session | ❌ (AI mode: ✅) |
review_adr |
Score ADR quality and get improvement suggestions | ✅ |
update_adr_status |
Transition ADR through its lifecycle | ❌ |
link_adrs |
Create relationships between ADRs | ❌ |
get_adr_graph |
Visualize the ADR dependency graph | ❌ |
check_stale_adrs |
Find old Accepted ADRs that need revisiting | ❌ |
search_decisions |
Keyword search across all past decisions | ❌ |
get_timeline |
Decision history for a project | ❌ |
`generate_adr` example output
# ADR-1: Adopt Redis as the caching layer
## Status
Accepted
## Context
We needed pub/sub support for real-time notifications.
Memcached only handles simple key-value caching and could not meet this requirement.
## Decision
We adopted Redis as both cache and message broker.
It supports pub/sub, TTL, and persistence, and the team already has operational experience with it.
## Consequences
Real-time features can now be imp