geo-mcp

Useful for

Use cases llm-inferred

Desk-based site context screening: geocode an address, buffer 1-2 km, then pull OSM features (e.g. waterways, buildings) for a constraints check · Preliminary civils or drainage gradient checks: elevation profile along a proposed route or corridor · Terrain screening: sample and zonal stats of a client-supplied GeoTIFF DEM over a site boundary · Drive-time accessibility isochrones for planning or appraisal reports (requires OpenRouteService key)

Audience llm-inferred

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

Limitations

Constraints docs-verified

Release status: PyPI provides v0.3.0; the v0.4.0 release candidate (newest provider and hardening work) is not yet released · Default public providers have usage policies: Nominatim max 1 request/second, OSRM demo server not for production, Overpass fair use · Isochrones require GEO_MCP_ORS_API_KEY, which is unset by default · Docs are inconsistent on tool count (44 in places, 42 in CLI output) · Roadmap items not yet available: Mapbox/Google geocoding, WebSockets, batch file processing, reproject/clip/mosaic · No UK-specific datasets or hydrological time-series (gauge levels, rainfall) documented · Raster and vector tools operate on local files supplied by the user; no bundled datasets documented

Example tool calls docs-verified

{
  "tool": "geocode",
  "arguments": {
    "query": "Brandenburg Gate, Berlin"
  }
}

{
  "tool": "buffer",
  "arguments": {
    "point": {
      "lat": 52.5163,
      "lon": 13.3777
    },
    "distance_m": 1000
  }
}