Skip to main content
Glama
Mhdd-24

@mhdd_24/adr-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @mhdd_24/adr-mcp

No user-submitted related servers found.

    Related Servers

    • ArchLens

      ptrivedi74
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to create, list, and read numbered Markdown Architecture Decision Records, and to review designs against pluggable domain rule packs (general, insurance, banking, healthcare, agentic AI) that return PASS/FAIL/UNKNOWN verdicts with evidence. Supports custom rule packs supplied via a local directory of YAML files.
      MIT

    • Alethea

      fpavia111-creator
      A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to persist and retrieve ADR-style decisions and machine-checkable constraints as git-friendly markdown in a repository, linked to requirement ids, tests and commits. Agents can pull relevant context before a task, check a proposed change against accepted constraints before committing, and record, supersede or search decisions over a local stdio connection.
      7
      143 npm
      MIT

    • adm-mcp

      fpavia111-creator
      A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to record, search, and supersede ADR-style decisions and machine-checkable constraints stored as git-friendly markdown in a repository, linked to SpecGate requirement ids, tests and commits. It also surfaces the relevant constraints and decisions for a task and checks a proposed change or diff for conflicts before it is committed.
      7
      0
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    Three tools is well-scoped for a focused ADR management server, covering the essential actions without unnecessary complexity.

    Completeness3/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources