Arcgis Austin
Server Details
City of Austin GIS — Austin, Texas open geospatial data (ArcGIS).
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-arcgis-austin
- GitHub Stars
- 0
- Server Listing
- mcp-arcgis-austin
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Within the ArcGIS trio (search_datasets, layer_info, query_layer) the boundaries are clean, but the other 44 tools contain heavily overlapping entry points: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools and suggest_questions all plausibly claim 'start here', and entity_profile vs company_facts vs compare_entities vs recent_changes vs company_register_search vs resolve_entity require reading long descriptions to separate. The Polymarket family (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread, resolution_audit, resolution_diff, updown_*) is at least articulated by descriptions, but selection still demands careful reading rather than obvious naming.
Nearly everything is lowercase snake_case with a verb_noun or noun_noun shape (search_datasets, query_layer, company_register_search, polymarket_fill_risk, resolution_audit), which is predictable and readable. The deviations are minor and local: single-word verbs (remember, recall, forget, subscribe, unsubscribe) and suffix variants (ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded) that read more as versioning than as distinct operations.
The server is named 'Arcgis Austin' yet only three of 47 tools (search_datasets, layer_info, query_layer) touch Austin GIS data; the remaining 44 are a broad Pipeworx data-gateway catalog spanning SEC filings, prediction markets, LLM visibility auditing, npm dependency scanning and CRM-style row research. That is both an extreme scope mismatch for the stated purpose and well past the 25+ threshold where a set becomes unwieldy.
For the apparent ArcGIS Austin domain the surface is thin: you can search datasets, inspect a layer schema, and run a single where-clause query, but there is no geometry/spatial filter, no aggregation or statistics, no geocoding, no export, and no write operations. The unrelated bulk of the catalog does not compensate, since almost none of it extends the GIS capability a caller would expect from this server name.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
City of Houston GIS — Houston, Texas open geospatial data (ArcGIS).
City of Round Rock GIS — Round Rock, Texas open geospatial data (ArcGIS).
City of Cedar Park GIS — Cedar Park, Texas open geospatial data (ArcGIS).
City of Pflugerville GIS — Pflugerville, Texas open geospatial data (ArcGIS).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceCity of San Bernardino GIS — San Bernardino, California open geospatial data (ArcGIS).56 npmMIT
- AlicenseNot gradedqualityCmaintenanceSarpy County GIS — Sarpy County, Nebraska open geospatial data (ArcGIS).60 npmMIT
- AlicenseNot gradedqualityCmaintenanceLincoln County GIS — Lincoln County, North Carolina open geospatial data (ArcGIS).69 npmMIT
- AlicenseNot gradedqualityCmaintenanceSt. Louis County GIS — St. Louis County, Missouri open geospatial data (ArcGIS). Enables searching and querying datasets like parcels, addresses, zoning and public works.61 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.