@mhdd_24/adr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADR_DIR | Yes | ADR directory |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| adr_statusC | Show ADR directory. |
| adr_listB | List ADR files. |
| adr_newC | Generate a new ADR markdown stub. |
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 3 tools
adr_status and adr_list overlap in purpose, both providing visibility into ADRs (directory vs. files), which could confuse an agent. adr_new is clearly distinct as a creation action.
All tools share the adr_ prefix, making the pattern predictable. However, suffixes mix nouns and verbs (status, list, new) rather than following a strict verb_noun convention.
Three tools is well-scoped for a focused ADR management server, covering the essential actions without unnecessary complexity.
Creating and listing ADRs are covered, but there is no tool to view the content of a specific ADR, nor update or delete records. This leaves a notable gap in the lifecycle.