A
licenseNot graded
qualityC
maintenanceEnables AI agents to record and retrieve architectural decision records, check precedent before making decisions, and avoid repeating past mistakes or contradicting settled choices.
34 PyPI
4
Apache 2.0
mcp-server-decisions
by Roberton003
Related Servers
Alternatives to mcp-server-decisions
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn LLM-native decision tracking system that captures unexpected engineering outcomes as 'pressure events' to build a persistent learning foundation. It enables AI assistants to manage cases, log surprises, and promote recurring insights into global or project-specific knowledge bases.22 npmMIT
- AlicenseNot gradedqualityAmaintenanceThe decision system for agentic engineering: keeps your project's decisions, rationale, and rejected paths in plain files and surfaces them to AI coding agents before they plan or change code.10Apache 2.0
- AlicenseAqualityCmaintenanceAuto-captures decision context from multi-agent workflows to preserve the 'why' behind every choice. Enables task traceability, reasoning retrieval, and continuous improvement across planning and implementation sessions.178 npm6MIT
- AlicenseNot gradedqualityDmaintenancePersistent decision memory and contradiction detection for AI coding agents. Enforces architectural consistency across sessions — the agent cannot code until it loads prior decisions. Human resolves conflicts on a dashboard or in chat.1MIT
- AlicenseNot gradedqualityAmaintenanceArchitectural decision tracker with staleness detection — records decisions and alerts when code changes invalidate them.MIT
TDQS
A3.9/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: querying decisions, recording a decision, recording a prediction for that decision, and recording the outcome. There is no overlap or ambiguity.
Naming Consistency5/5
All tool names follow the same pattern: a verb followed by a noun, using lowercase and hyphens (e.g., record-decision). The naming is perfectly consistent.
Tool Count5/5
Four tools cover the core workflow of managing decisions with predictions and outcomes. The count is appropriate for this focused domain, not too few or too many.
Completeness4/5
The tool set covers the main lifecycle: querying, recording decisions, adding predictions, and logging outcomes. Missing update or delete functionality, but the core workflow is complete.
Maintenance
ActivityMaintained
ResponsivenessNo issues