capetown-opendata-mcp

Useful for

Use cases llm-inferred

Site constraints screening: heritage inventory sites and land parcels within a bounding box for a Cape Town development · Planning context: ward boundaries and land parcels (erven) for a site's suburb · Water quality baseline: recent inland water quality sampling results for a study area · Planning precedent review: building plan approval counts by area using summarize_layer

Audience llm-inferred

GIS analysts · planners · environmental consultants · hydrologists · civils engineers

Limitations

Constraints llm-inferred

Covers City of Cape Town open data only; it does not provide UK data · Two ArcGIS servers are used; record counts differ between them on some layers, so the --server setting matters · Responses are capped at about 8,000 tokens by default, so large results need paging, fewer fields, or centroid geometry · service_requests and building_plan_approvals are non-spatial tables, so they take no bbox or polygon filters; use summarize_layer for counts · Published layer IDs can drift when the portal is republished, so discovery via service_info is preferred over hard-coded IDs · Some ODP_SPLIT services may be temporarily unavailable; service_info reports these · No data update frequency is stated; the default response cache TTL is 5 minutes · Maintenance relies partly on sponsorship, which the docs request for triage and dependency bumps

Example tool calls docs-verified

{
  "tool": "wards",
  "arguments": {
    "limit": 5
  }
}