get_scenario_details — Mitigant MCP Tool Read-only
get_scenario_details
(get scenario details) is one of 14 tools on the
Mitigant
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_scenario_details from your client
- Claude Code Mitigant get_scenario_details run in your project directory
- Claude Desktop Mitigant get_scenario_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Mitigant get_scenario_details ~/.cursor/mcp.json
- VS Code Mitigant get_scenario_details .vscode/mcp.json
- Zed Mitigant get_scenario_details ~/.config/zed/settings.json
- Windsurf Mitigant get_scenario_details ~/.codeium/windsurf/mcp_config.json
- Cline Mitigant get_scenario_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Mitigant get_scenario_details ~/.gemini/settings.json
- Grok Mitigant get_scenario_details .mcp.json (in your project root)
- ChatGPT Mitigant get_scenario_details Settings → Connectors → Advanced → Developer mode
- Claude.ai Mitigant get_scenario_details Settings → Connectors → Add custom connector
- LangChain Mitigant get_scenario_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mitigant-mcp https://mcp.mitigant.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.