NestDaddy

Who Do I Call For? — Emergency Home-Service Router

io.github.woodydaniel/whodoicallfor · v1.1.0

Routes home emergencies to the right trade: who to call in what order, first steps, sourced costs.

Connect Remote server

Terminal
claude mcp add --transport http whodoicallfor https://whodoicallfor.com/api/mcp/
~/.cursor/mcp.json
{
  "mcpServers": {
    "whodoicallfor": {
      "url": "https://whodoicallfor.com/api/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "whodoicallfor": {
      "type": "http",
      "url": "https://whodoicallfor.com/api/mcp/"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://whodoicallfor.com/api/mcp/

Tools 3 found in our last check

  • route_emergency

    Given a home emergency described in plain words (e.g. "water coming through my ceiling"), returns the matching situation(s): who to call and in what order, first steps, typical costs, and a 24/7 dispatch phone number when one is available for the service vertical. Optionally pas…

  • get_scenario

    Fetch one situation in full: structured answer (who to call, costs, FAQ, sources) plus the complete step-by-step guide as markdown. Use category and slug values from route_emergency or list_scenarios.

  • list_scenarios

    List every published situation with title, category, slug, and canonical URLs.

Details

Endpointhttps://whodoicallfor.com/api/mcp/ (Streamable HTTP)
First published12 Aug 2026
Last updated12 Aug 2026
Registry nameio.github.woodydaniel/whodoicallfor

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.