INDIVIDUAL MCP TOOL
get_scenario
Fetch one situation in full: structured answer (who to call, costs, FAQ, sources) plus the complete step-by-step guide as markdown.
LIVE ENDPOINT
https://whodoicallfor.com/api/mcp
Connect to this endpoint to inspect the live schema for get_scenario and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- A tool name or description suggests retrieving external content.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.whodoicallfor]
url = "https://whodoicallfor.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"whodoicallfor": {
"type": "http",
"url": "https://whodoicallfor.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: whodoicallfor
Remote MCP URL: https://whodoicallfor.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"whodoicallfor": {
"url": "https://whodoicallfor.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"whodoicallfor": {
"type": "http",
"url": "https://whodoicallfor.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "whodoicallfor",
"transport": "streamable-http",
"url": "https://whodoicallfor.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
route_emergency— Given a home emergency described in plain words (e.list_scenarios— List every published situation with title, category, slug, and canonical URLs.