A
licenseNot graded
qualityC
maintenanceAn MCP server that turns a folder of Markdown ADRs into live tools for AI agents: search, author, validate, link, and trace architectural decisions, with preview-by-default writes.
1
MIT
biz.dfch.SpecMgr
by dfch
Related Servers
Alternatives to biz.dfch.SpecMgr
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server for discovering and validating Architecture Decision Records, inspecting architecture impact, and reviewing architectural drift evidence.20MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceMCP server that manages C4 architecture models, ADRs, and flow diagrams as TOML files in a docs directory, with git versioning and an HTTP viewer.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for managing an OKF markdown knowledge base, enabling AI agents to query, read, write, and auto-sync architectural decisions and rules via Git.MIT
- FlicenseNot gradedqualityCmaintenanceShared project memory MCP server for storing and retrieving technical decisions, lessons learned, ADRs, and cross-links between projects.-
TDQS
A3.5/5.0
Scored across 124 tools
Disambiguation4/5
Each tool targets a distinct (domain, action) pair — create_prb vs create_req vs get_tsk etc. are clearly separated by domain token, and the generic update/edit/delete/set_status/set_classification are clearly scoped. There is mild ambiguity between parallel families (get_X id-based read vs parse_X path-based parse, update vs edit vs option_update vs update_section, get_reference_diagram vs _all), but descriptions disambiguate well.
Naming Consistency3/5
Most tools follow verb_domain (create_prb, get_tsk, list_gol, parse_sysrs), but there is notable inconsistency: bare verbs with no noun (update, edit, delete, validate, mdformat), noun_verb reversal (option_create, option_list, option_read), mixed uc vs use_case spelling (get_uc_schema vs get_use_case_package_diagram), and some domain-in-name vs domain-as-parameter splits.
Tool Count2/5
124 tools for a 14-domain spec manager is heavy; while the per-domain parallelism (create/get/list/parse/template/example/schema for ~13 domains) partially justifies the count, it is far past the practical ceiling for agent navigation and surfaces many rarely-needed variants.
Completeness4/5
Coverage is very strong: full create/get/list/validate/update/edit/delete lifecycle across 13 whole-body domains plus ADR-specific tools, references, similarity search, diagrams, and translation drift. Minor gaps: ADR is excluded from delete/set_status/set_classification/validate generic tools and has no delete_adr, leaving some ADR lifecycle dead ends.
Maintenance
ActivityActive
ResponsivenessLimited data