scenario_council — Batcave Detective Basic MCP Tool
scenario_council
(scenario council) is one of 5 tools on the
Batcave Detective Basic
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call scenario_council from your client
- Claude Code Batcave Detective Basic scenario_council run in your project directory
- Claude Desktop Batcave Detective Basic scenario_council ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Batcave Detective Basic scenario_council ~/.cursor/mcp.json
- VS Code Batcave Detective Basic scenario_council .vscode/mcp.json
- Zed Batcave Detective Basic scenario_council ~/.config/zed/settings.json
- Windsurf Batcave Detective Basic scenario_council ~/.codeium/windsurf/mcp_config.json
- Cline Batcave Detective Basic scenario_council ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Batcave Detective Basic scenario_council ~/.gemini/settings.json
- Grok Batcave Detective Basic scenario_council .mcp.json (in your project root)
- ChatGPT Batcave Detective Basic scenario_council Settings → Connectors → Advanced → Developer mode
- Claude.ai Batcave Detective Basic scenario_council Settings → Connectors → Add custom connector
- LangChain Batcave Detective Basic scenario_council pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http batcave-detective https://subsidy-stylized-unaligned.ngrok-free.dev/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.