simulate_remediation — CausalLayer MCP MCP Tool
simulate_remediation
(simulate remediation) is one of 10 tools on the
CausalLayer MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call simulate_remediation from your client
- Claude Code CausalLayer MCP simulate_remediation run in your project directory
- Claude Desktop CausalLayer MCP simulate_remediation ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CausalLayer MCP simulate_remediation ~/.cursor/mcp.json
- VS Code CausalLayer MCP simulate_remediation .vscode/mcp.json
- Zed CausalLayer MCP simulate_remediation ~/.config/zed/settings.json
- Windsurf CausalLayer MCP simulate_remediation ~/.codeium/windsurf/mcp_config.json
- Cline CausalLayer MCP simulate_remediation ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CausalLayer MCP simulate_remediation ~/.gemini/settings.json
- Grok CausalLayer MCP simulate_remediation .mcp.json (in your project root)
- ChatGPT CausalLayer MCP simulate_remediation Settings → Connectors → Advanced → Developer mode
- Claude.ai CausalLayer MCP simulate_remediation Settings → Connectors → Add custom connector
- LangChain CausalLayer MCP simulate_remediation pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http causallayer https://mcp.faultkey.com/mcpOther tools on this server
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.