get_county_outlook — Homecastr Remote MCP MCP Tool Read-only
get_county_outlook
(get county outlook) is one of 44 tools on the
Homecastr Remote MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_county_outlook from your client
- Claude Code Homecastr Remote MCP get_county_outlook run in your project directory
- Claude Desktop Homecastr Remote MCP get_county_outlook ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Homecastr Remote MCP get_county_outlook ~/.cursor/mcp.json
- VS Code Homecastr Remote MCP get_county_outlook .vscode/mcp.json
- Zed Homecastr Remote MCP get_county_outlook ~/.config/zed/settings.json
- Windsurf Homecastr Remote MCP get_county_outlook ~/.codeium/windsurf/mcp_config.json
- Cline Homecastr Remote MCP get_county_outlook ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Homecastr Remote MCP get_county_outlook ~/.gemini/settings.json
- Grok Homecastr Remote MCP get_county_outlook .mcp.json (in your project root)
- ChatGPT Homecastr Remote MCP get_county_outlook Settings → Connectors → Advanced → Developer mode
- Claude.ai Homecastr Remote MCP get_county_outlook Settings → Connectors → Add custom connector
- LangChain Homecastr Remote MCP get_county_outlook pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http homecastr-remote https://www.homecastr.com/api/mcp/mcpOther tools on this server
- forecast_by_address
- forecast_by_parcel
- forecast_by_tabblock
- forecast_by_tract
- forecast_by_zcta
- forecast_by_unit
- forecast_by_county
- forecast_by_state
- forecast_by_zip3
- forecast_by_h3_cell
- get_permit_zoning_readiness
- get_census_bps_county_monthly
- get_fast41_projects
- get_epa_echo_npdes_sewer_overflows
- get_epa_echo_npdes_outfalls
- get_epa_echo_npdes_sewer_overflow_history
- get_epa_echo_npdes_violations
- list_benchmark_datasets
- get_benchmark_dataset
- get_public_forecast_vintage
- get_backtest_scores
- list_data_assets
- get_data_asset
- list_data_sources
- get_data_source
- get_panel_lineage
- get_data_coverage
- list_source_coverage_index
- list_public_records_acquisition
- get_source_coverage_map
- list_data_schemas
- get_data_schema
- get_entity
- get_geography_crosswalk
- get_provenance
- get_data_artifact
- get_forecast_vintage
- get_benchmark_result
- list_benchmark_sources
- list_training_runs
- get_analytics_events
- get_api_status
- get_api_usage
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.