$ loading_
Log and retrieve decisions with provenance, supersession, and audit trails.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "Decision Log" MCP server from askskill: Run: claude mcp add --transport http 'ai-decisionlog-mcp' 'https://www.decisionlog.ai/api/mcp'
Append the following as a decision log entry: change mobile login from SMS codes to email codes; reason: SMS costs are too high and international delivery failure is high; provenance includes this month's cost report and customer support ticket summary.
Returns the appended decision entry with the decision, rationale, provenance, and an auditable record.
Retrieve all historical decisions related to "login method" and list which ones are still active and which have been superseded.
Returns matching decisions with status, timestamps, and whether each one was superseded by a later decision.
Add a new decision: restore SMS codes as a backup login method for overseas users, and mark it as superseding the May 2024 login decision; provenance is the latest usability test results.
Returns the new decision and its supersession link, making the decision history traceable.
Product managers or engineering teams use it to append decisions during requirement changes or architecture trade-offs. This preserves provenance and makes the full decision chain easy to review later.
When an old decision is replaced by a new one, teams can record the supersession relationship to avoid relying on outdated conclusions. This makes it easier to identify the currently valid decision.
Teams that need operational auditability can use it to record decisions tied to MCP actions. This helps explain who decided what and based on which information during audits, compliance reviews, or post-incident analysis.
It is an MCP tool for append-only decision logging with provenance, supersession, retrieval, and audited actions. It fits workflows that need traceable decision history.
Yes. The description explicitly mentions supersession, which indicates it can record when a later decision replaces an earlier one and distinguish current from historical decisions.
The provided material does not include installation steps, runtime requirements, or key prerequisites. See the source repository for those details.
Create tamper-evident audit logs for AI decisions and compliance evidence.
Keep verifiable, tamper-evident audit logs of AI agent actions.
Lets AI check a team's decision ledger before acting on past decisions.
Create tamper-evident signed audit logs for agent calls, handoffs, and decisions
Automatically document development journeys, code snippets, and project records for easy retrieval.
Run recursive decision rollouts with visible evidence trails and option comparisons.