decision_log_lock_decision — Decision Log MCP Tool
decision_log_lock_decision
(decision log lock decision) is one of 30 tools on the
Decision Log
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call decision_log_lock_decision from your client
- Claude Code Decision Log decision_log_lock_decision run in your project directory
- Claude Desktop Decision Log decision_log_lock_decision ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Decision Log decision_log_lock_decision ~/.cursor/mcp.json
- VS Code Decision Log decision_log_lock_decision .vscode/mcp.json
- Zed Decision Log decision_log_lock_decision ~/.config/zed/settings.json
- Windsurf Decision Log decision_log_lock_decision ~/.codeium/windsurf/mcp_config.json
- Cline Decision Log decision_log_lock_decision ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Decision Log decision_log_lock_decision ~/.gemini/settings.json
- Grok Decision Log decision_log_lock_decision .mcp.json (in your project root)
- ChatGPT Decision Log decision_log_lock_decision Settings → Connectors → Advanced → Developer mode
- Claude.ai Decision Log decision_log_lock_decision Settings → Connectors → Add custom connector
- LangChain Decision Log decision_log_lock_decision pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://www.decisionlog.ai/api/mcpOther tools on this server
- decision_log_create_decision
- decision_log_search_decisions
- decision_log_get_decision
- decision_log_supersede_decision
- decision_log_approve_decision_action
- decision_log_get_decision_governance
- decision_log_list_recent_decisions
- decision_log_submit_source
- decision_log_list_sources
- decision_log_get_source
- decision_log_get_source_decisions
- decision_log_list_candidates
- decision_log_get_candidate
- decision_log_create_candidate
- decision_log_resolve_candidate
- decision_log_convert_candidate_to_supersession
- decision_log_get_current_decision
- decision_log_get_supersession_history
- decision_log_get_decision_sources
- decision_log_list_audit_events
- decision_log_list_decisions_by_tag
- decision_log_list_decisions_by_domain
- decision_log_render_decision
- decision_log_render_workspace_brief
- decision_log_render_decision_explorer
- decision_log_render_candidate_review
- decision_log_render_supersession_composer
- decision_log_render_source_pipeline
- decision_log_render_audit_explorer
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.