mcp-adr
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADR_DIR | No | Directory where ADR markdown files live | docs/adr |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| adr_createC | Create a new ADR with the given title and optional content. |
| adr_readC | Read an ADR by number or title substring. Returns structured content. |
| adr_updateC | Overwrite an existing ADR with new markdown content. |
| adr_listC | List all ADRs, optionally filtered by status and/or type. |
| adr_searchC | Full-text search across all ADRs. |
| adr_update_statusD | Change the status of an existing ADR. |
| adr_supersedeB | Mark an ADR as superseded by another ADR, linking both. |
| adr_deprecateD | Deprecate an ADR with a reason. |
| adr_linkB | Add a bidirectional related link between two ADRs. |
| adr_historyC | Find ADRs matching a query, returned as a timeline sorted by date. |
| adr_diagramC | Generate or retrieve a diagram for an ADR. |
| adr_overviewC | Generate an overview diagram of all ADRs (optionally filtered by status). |
| adr_impactC | Find all ADRs that mention a component. |
| adr_dependenciesC | Build the dependency graph of ADRs, optionally filtered to one ADR's transitive deps. |
| adr_exportC | Export all ADRs to HTML. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool has a distinct purpose (create, read, update, list, search, deprecate, supersede, link, dependencies, diagram, export, history, impact, overview). No two tools overlap in functionality, making it easy for an agent to select the correct one.
All tools share the 'adr_' prefix, but the stems vary between verbs (adr_create, adr_read) and nouns (adr_dependencies, adr_overview). This is mostly consistent and readable, with minor deviation from a strict verb_noun pattern.
With 15 tools, the server covers the full lifecycle of ADR management without being overly granular or sparse. Each tool serves a clear purpose within the domain.
The tool set covers all core operations (CRUD, search, status changes) and extends to advanced features like dependency graphs, diagrams, export, and impact analysis. There are no obvious gaps for typical ADR workflows.