CLIO Terrain
Wire DEM slope, aspect, suitability, and point-cloud gridding into Claude Code or Cursor when you build mapping, drone, or outdoor-location products.
Overview
io.github.iowarp/terrain-mcp is a MCP server for the Build phase that runs DEM slope, aspect, and suitability analysis plus point-cloud reading and gridding for agent-driven terrain workflows.
What is this MCP server?
- Digital elevation model (DEM) slope, aspect, and suitability analysis
- Point-cloud reading and gridding workflows
- stdio MCP transport via clio-kit on PyPI (v2.2.3)
- Backed by iowarp/clio-kit on GitHub
- Suited to GIS-heavy agent workflows without custom GDAL scripting each session
- Server schema version 2025-12-11; package version 2.2.3
- stdio transport via PyPI identifier clio-kit
- Repository: github.com/iowarp/clio-kit
Community signal: 25 GitHub stars.
What problem does it solve?
Geospatial terrain and point-cloud steps usually live outside your agent session in GDAL scripts or desktop GIS, which slows iteration when you are building location-aware features solo.
Who is it for?
Indie builders adding DEM or LiDAR-style analysis to mapping, outdoor, or logistics products who already work in Python-friendly agent setups.
Skip if: Teams that only need simple lat/long IP lookup or who have no raster or point-cloud data in their stack.
What do I get? / Deliverables
Your agent can request structured terrain and point-cloud operations over MCP so geospatial checks stay in the same coding loop as your app integration work.
- Agent-callable DEM slope, aspect, and suitability results
- Point-cloud read and grid outputs for downstream app or pipeline use
Recommended MCP Servers
Journey fit
Terrain and point-cloud analysis is an integration layer you add while implementing geospatial features, not a launch or growth marketing task. CLIO Terrain exposes analysis tools over MCP stdio via the clio-kit PyPI package—classic backend/integration work for agent-driven geoprocessing.
How it compares
Specialized terrain and point-cloud MCP integration, not a general web search or IP geolocation server.
Common Questions / FAQ
Who is io.github.iowarp/terrain-mcp for?
Solo and small-team builders shipping geospatial or field-data features who want DEM and point-cloud tools callable from Claude Code, Cursor, or similar MCP clients.
When should I use io.github.iowarp/terrain-mcp?
Use it during Build when you are integrating slope, aspect, suitability, or gridded point-cloud outputs into a product, pipeline, or agent-assisted analysis workflow.
How do I add io.github.iowarp/terrain-mcp to my agent?
Install the clio-kit PyPI package (v2.2.3), configure stdio MCP transport in your client, and point the server entry at this terrain MCP package per your host’s MCP settings.