Terrain
MCP server for terrain analysis: DEM slope/aspect/suitability and point-cloud reading/gridding
claude mcp add --scope project clio-terrain -- clio-kit mcp-server terrain
Install the launcher first. Restart your client after setup. Configuration locations →
Check the connection
clio-kit doctor --server terrain --connect
Checks prerequisites and tool discovery. Test on known input to verify results. Native backends may require additional setup.
Tools
dem_terrainAnalyze a Digital Elevation Model grid for elevation, slope, aspect, and site suitability. Accepts CSV numeric grids, NPY, and NPZ (with a 'dem' array); GeoTIFF requires the optional rasterio extra. Returns grid shape, summary statistics, suitability counts, and representative suitable cells.
pointcloud_readRead an x/y/z point cloud and grid it into a DEM-like surface by averaging z per cell. Accepts CSV with x,y,z columns, NPY, and NPZ; LAS/LAZ requires the optional laspy extra. Optionally writes the gridded surface to a CSV DEM for downstream dem_terrain analysis. Returns point/grid stats and bounds.
Examples
Replace example paths with your own files and check the returned results.
Analyze an elevation grid
Use dem_terrain with a supported CSV numeric grid, NPY or NPZ array. Establish
cell spacing and horizontal/vertical units before interpreting slope, aspect or
suitability. GeoTIFF requires optional rasterio support.
Grid a point cloud
pointcloud_read averages x/y/z points into cells and can write a CSV DEM for
dem_terrain. Choose cell size deliberately and retain the source. Ground and
canopy values in one cell are averaged together; this is not ground classification.
LAS/LAZ requires optional laspy support.