Skillget

capetown-opendata-mcp

mcp
Guvenlik Denetimi
Uyari
Health Uyari
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 5 GitHub stars
Code Gecti
  • Code scan — Scanned 10 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested

Bu listing icin henuz AI raporu yok.

SUMMARY

A comprehensive MCP server for accessing Capetown Opendata

README.md

capetown-opendata-mcp

A comprehensive Model Context Protocol (MCP) server that
exposes the City of Cape Town Open Data Portal to MCP
clients such as Claude Desktop, Claude Code, and any other MCP-compatible host.

It wraps capetown-opendata and
go-arcgis, turning the City's ArcGIS Feature
Service into a set of LLM-callable tools with discovery, a generic query escape hatch, spatial
and attribute filtering, and in-memory response caching.

Website: richardwooding.github.io/capetown-opendata-mcp

Tools

Tool Description
load_shedding_blocks Load shedding block polygons (block geometry and ID).
wards Municipal ward boundaries (ward name, year).
land_parcels Cadastral land parcels (erven); optional suburb filter (case-insensitive).
taxi_routes Registered minibus taxi routes.
water_quality Inland water quality sampling results (a non-spatial table), newest first.
public_lighting Public street lighting assets.
heritage_inventory Heritage inventory sites and features.
query_layer Generic query over any layer by service + layer_id (where/fields/order/bbox/offset/count-only).
field_values List the distinct values of a field on a layer (service + layer_id); discover valid filter values.
service_info List every layer/table across all split services, each tagged with its host service; name_contains filters the listing.
layer_info Describe a layer's fields, geometry type, and page size (service + layer_id).

Every feature-returning tool accepts a shared set of filters: limit (default 200, max 2000),
offset (skip N features; pair with the next_offset in the response to page through a layer),
where (extra SQL filter, AND-combined), bbox ([minLon, minLat, maxLon, maxLat] in WGS84),
polygon (rings [[[lon,lat],…],…] in WGS84, for irregular areas like a ward boundary),
include_geometry (default false), omit_nulls (drop null-valued attributes), and
use_aliases (rename raw column names to their human-readable field aliases). Spatial filters are
sent as WGS84 (inSR=4326), so they work against layers stored in any projection.

Note: The City of Cape Town publishes its Open Data across a dozen split feature services
(ODP_SPLIT_1 … ODP_SPLIT_12); a layer is addressed by both a service and a layer_id.
service_info aggregates all of them into one catalogue (each entry tagged with its host
service), and reports any split that is temporarily unavailable. Use it to discover the
service + layer_id to pass to layer_info, field_values, and query_layer. Published IDs
occasionally drift as the portal is republished, so prefer discovery over hard-coded IDs.

Install

MCP Bundle (Claude Desktop, one-click)

Every release attaches
MCP Bundles (.mcpb) — one per platform. Download the bundle matching your OS and
architecture (e.g. capetown-opendata-mcp_<version>_darwin_arm64.mcpb) and open it with
Claude Desktop to install. The bundle's settings screen lets you set an optional ArcGIS
token, request timeout, and cache TTL.

Homebrew (macOS / Linux)

brew install richardwooding/tap/capetown-opendata-mcp

Container image

docker run -i --rm ghcr.io/richardwooding/capetown-opendata-mcp:latest

From source

go install github.com/richardwooding/capetown-opendata-mcp@latest

Usage

By default the server speaks the MCP stdio transport:

capetown-opendata-mcp

Claude Desktop / Claude Code config

{
  "mcpServers": {
    "capetown-opendata": {
      "command": "capetown-opendata-mcp"
    }
  }
}

HTTP transport

For remote or containerized deployments, run the streamable-HTTP transport:

capetown-opendata-mcp --transport http --http-addr :8080

Configuration

All flags can also be set via environment variables (prefix CAPETOWN_MCP_):

Flag Env Default Description
--transport CAPETOWN_MCP_TRANSPORT stdio stdio or http.
--http-addr CAPETOWN_MCP_HTTP_ADDR :8080 Listen address for the HTTP transport.
--timeout CAPETOWN_MCP_TIMEOUT 30s Per-request upstream timeout.
--cache-ttl CAPETOWN_MCP_CACHE_TTL 5m Response cache TTL (0 disables caching).
--arcgis-token CAPETOWN_MCP_ARCGIS_TOKEN (none) Optional ArcGIS token for authenticated services.

Development

go build ./...
go test -race ./...
golangci-lint run
goreleaser release --snapshot --clean   # local dry run

Releasing

Pushing a vX.Y.Z tag triggers the release workflow, which uses
GoReleaser to:

  • build binaries for linux/darwin/windows (amd64 + arm64),
  • pack each binary into an MCP Bundle (.mcpb) and attach all six to the release,
  • build and push a multi-arch OCI image to GHCR with ko,
  • publish a Homebrew cask to richardwooding/homebrew-tap.

The release requires a HOMEBREW_TAP_GITHUB_TOKEN repository secret (a PAT with repo scope on
the tap). GHCR uses the built-in GITHUB_TOKEN.

MCP Bundles

tools/mcpb is a small, dependency-free (Go stdlib) packer that zips the server binary and a
generated manifest.json into a .mcpb. GoReleaser invokes it per build target, but you can
build a bundle for your current platform locally (no Node required):

go build -o capetown-opendata-mcp .
go run ./tools/mcpb pack -version dev

Because the manifest format selects a binary by OS only (not architecture), each release ships
one bundle per OS+arch.

License

MIT — see LICENSE.

Yorumlar (0)

Sonuc bulunamadi