Who Do I Call For? MCP MCP server

This MCP server provides tools for routing home emergencies to the correct trade, offering ranked situations, first steps, typical costs, and dispatch numbers. It supports querying specific scenarios, listing all published situations, and routing emergencies based on plain-language problem descriptions and US state codes.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Who Do I Call For?

MCP endpoint (Streamable HTTP)

https://whodoicallfor.com/api/mcp/

Vendor documentation

What you can do with it

Route home emergencies to the right trade
Get step-by-step repair guides
List all published emergency scenarios
Find region-aware dispatch numbers

Tools advertised by the last live check:

route_emergency
get_scenario
list_scenarios

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http who-do-i-call-for-mcp https://whodoicallfor.com/api/mcp/

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add who-do-i-call-for-mcp --url https://whodoicallfor.com/api/mcp/

Cursor

Merge this server into .cursor/mcp.json in your project, then enable who-do-i-call-for-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "who-do-i-call-for-mcp": {
      "url": "https://whodoicallfor.com/api/mcp/"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "who-do-i-call-for-mcp": {
      "type": "streamableHttp",
      "url": "https://whodoicallfor.com/api/mcp/",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start who-do-i-call-for-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "who-do-i-call-for-mcp": {
      "type": "http",
      "url": "https://whodoicallfor.com/api/mcp/"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http who-do-i-call-for-mcp https://whodoicallfor.com/api/mcp/

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "who-do-i-call-for-mcp": {
      "url": "https://whodoicallfor.com/api/mcp/"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "who-do-i-call-for-mcp": {
      "serverUrl": "https://whodoicallfor.com/api/mcp/"
    }
  }
}

See all 1,687

Do you run Who Do I Call For? MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing