Altitude for any point or path.

Heights in metres above sea level, with summary statistics for total ascent and descent.

mcp.footstep.ai / get_elevation

Why you need it

Why your agent needs this.

When the user asks 'how hilly is this walk?', the agent shouldn't render its own elevation chart. get_elevation returns the heights plus rolled-up ascent and descent in numbers the agent can quote directly. 'About 120 metres of climb' beats a raw array every time.

What it does for you

What your agent gets back.

Summary numbers (total ascent, descent, min, max) the agent can read out loud.
Per-point heights when the agent needs to render a profile chart.
Works on points OR a path geometry.
Composes with get_directions to enrich an existing route with terrain narrative.
Token-lean: drop the per-point array when you only need the summary.

Built for

For SAR teams For AI developers

Try it

Plug it into your agent.

Add Footstep to your MCP-aware runtime. Your model picks the tool at runtime; you wrote none of the orchestration.

Read the full reference

Prompt that triggers get_elevation

"What's the elevation profile between these two coordinates?"

claude_desktop_config.json

{
  "mcpServers": {
    "footstep": {
      "url": "https://mcp.footstep.ai",
      "headers": {
        "x-api-key": "sk_live_your_key_here"
      }
    }
  }
}

Related capabilities.

get_directions

Point-to-point or multi-stop routes with terrain analytics. Answer 'is this walkable?' without a second call.

snap_trace

Map-match a noisy GPS recording to the road network. Returns the corrected path plus per-segment road attributes.

get_isochrone

Reachability polygons by time or distance from any starting point. Walking, cycling, or driving.

Ready to call it?

£5 free credit on signup. One auth header, every major runtime.

Get an API key See the REST endpoint