GIS-MCP-Server

Useful for

Use cases llm-inferred

Batch-geocode up to 10 project addresses to coordinates for a site or consultee list · Elevation profile along a proposed drainage or pipe route for gradient screening · Buffer a site point or boundary by a set distance to define a consultation or search zone · Reproject layers between CRS (e.g. EPSG:4326 to EPSG:3857) before combining datasets

Audience llm-inferred

GIS analysts · drainage engineers · hydrologists · planners · civils engineers

Limitations

Constraints llm-inferred

DOCS describe 'LocuSync Server' (repo matbel91765/locusync-server, PyPI locusync-server), not 'GIS-MCP-Server' as named in ENTRY; confirm the docs belong to this entry's repo before publishing · Default geocoding is Nominatim/OSM, enforced at 1 request/second; Pelias is only used when PELIAS_URL is set (default empty) · Default routing uses the OSRM demo server, which is best effort; self-hosting is advised for production · batch_geocode is capped at 10 addresses per request · DOCS do not state the elevation data source, resolution or vintage (Open-Elevation is the default endpoint) · DOCS do not state UK or regional coverage, or any time span · Valhalla native isochrones, PostGIS queries and full ESRI FileGDB support are roadmap items and not complete · Python 3.11+ required (per README badge)

Example tool calls docs-verified

{
  "tool": "distance",
  "arguments": {
    "lat1": 52.4862,
    "lon1": -1.8904,
    "lat2": 51.5074,
    "lon2": -0.1278
  }
}