API & MCP

Everything a person can do on RavingDesk Terrain Analyzer (DEM slope, aspect, hillshade, contours), a program or AI agent can do with the same inputs and get the identical result.

HTTP API

• POST https://ravingdeskterrainanalyzer.usefulweb.site/api/v1/calculate – run RavingDesk Terrain Analyzer (DEM slope, aspect, hillshade, contours)
• GET https://ravingdeskterrainanalyzer.usefulweb.site/api/v1/tool – inputs, output schema, examples
• OpenAPI 3.1: /openapi.json · /openapi.yaml
• Errors: application/problem+json; 422 includes per-field errors.

Every result contains

inputs (normalised, defaults applied), summary, result (validated against the published schema), units, assumptions, sources, warnings, computedAt and links.

MCP (Model Context Protocol)

• Streamable HTTP endpoint: https://ravingdeskterrainanalyzer.usefulweb.site/mcp – protocol revisions 2026-07-28 (stateless) and 2025-11-25 / 2025-06-18 / 2025-03-26 (initialize handshake).
• Tools: ravingdesk_terrain_analyzer
• Local stdio connector: node src/mcp-stdio.ts --tool=ravingdesk-terrain-analyzer

{
  "mcpServers": {
    "ravingdesk-terrain-analyzer": { "type": "http", "url": "https://ravingdeskterrainanalyzer.usefulweb.site/mcp" }
  }
}