Labsco
MCP SERVER

Local Austin MCP

by mindwear-capitian ↗

Answer real Austin property questions — who supplies the water, what the taxes are, is it in a flood zone, what is for sale — straight from the authoritative city and county sources.

Real Estate & Property✓ Verified
Summary
Composed tools do the fan-out, so one address answers a dozen questions.

The single-source tools are useful, but the composed ones are the reason to install it: `austin_property_360` and `austin_relocation` hit appraisal, tax, flood, permits, schools and utilities in one call and come back with a `source_url` per record. Coverage stops at the Austin metro — it is a city-specific server by design, and the repo is the reference implementation for the same pattern in other cities.

What it is

A local-knowledge server for the Austin metro. Every tool hits an official source live — Travis, Williamson and Hays CAD, the Travis County Tax Office, data.austintexas.gov, FEMA, TEA, CapMetro, the National Weather Service — plus active MLS listings and neighbourhood pages provided by Neuhaus Realty Group. Every response carries a `source_url` so you can check the record yourself.

What you get
  • One address in, a full property picture out: appraisal, tax, flood zone, permits, code cases, 311 and zoning together — `austin_property_360`
  • The new-resident report: water and sewer provider, special-district taxes, school district and voter precinct, plus the Texas move-in checklist — `austin_relocation`
  • Who actually turns on the water at a Travis County address, with how-to-start guidance, from PUC CCN boundaries — `austin_utility_providers`
  • Active for-sale listings searchable by city, ZIP, school district or subdivision, and a single listing pulled by MLS ID or street address — `austin_active_listings`, `austin_listing_detail`, `austin_listing_by_address`
  • County appraisal and tax lookups across three counties — `austin_travis_cad`, `austin_williamson_cad`, `austin_hays_cad`, `austin_travis_tax`
  • Flood zone, permit history, code compliance, zoning and tree permits for any City of Austin address — `austin_fema_flood`, `austin_permits`, `austin_code_cases`, `austin_zoning`, `austin_tree_permits`
  • Civic and public-safety data: 311 requests, APD crime, live AFD dispatches, council votes, the open budget, restaurant inspection scores, animal shelter intakes — `austin_311`, `austin_crime`, `austin_afd_incidents`, `austin_council_votes`, `austin_city_budget`, `austin_restaurant_inspections`, `austin_animal_center`
  • Live CapMetro arrivals and vehicle positions on a 15-second feed, plus TxDOT projects and active work zones — `austin_next_bus`, `austin_txdot_projects`, `austin_roadway_work_zones`
  • Weather alerts, Highland Lakes reservoir levels with a 30-day trend, and trash, recycling and compost collection days — `austin_nws_alerts`, `austin_lake_travis_level`, `austin_trash_schedule`
  • A per-provider health check reporting status, HTTP code and latency for every upstream, so you can tell a dead provider from a broken tool — `austin_health`
Requirements

Nothing — no API keys for any tool. `npx -y github:mindwear-capitian/local-austin-mcp` over stdio is the whole setup; Node 20 or newer. Optional variables: `AUSTIN_SODA_APP_TOKEN` raises the Socrata rate limit, `LOCAL_AUSTIN_MCP_TIER` set to `core` registers only the 14 most-used tools if your client has a tool cap, and `AUSTIN_LIMIT_<SOURCE>` caps per-source concurrency. Apache 2.0.

Setup effort

One command — claude mcp add local-austin npx -y github:mindwear-capitian/local-austin-mcp