Where can you reach in 30 minutes?

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

mcp.footstep.ai / get_isochrone

Why you need it

Why your agent needs this.

When the user asks 'what's reachable from Kings Cross in 30 minutes', the agent needs a tool that takes a place name and a time budget and returns drawable polygons. get_isochrone does both: pass 'from' as text (geocoded internally) plus your contour list, get back render-ready polygons per contour band.

This tool bundles Geocoding + Reach analysis in a single call.

What it does for you

What your agent gets back.

Render envelope with one Polygon layer per contour, each carrying its contour value as a style hint.
Pass 'from' as a place name and the origin is geocoded for you.
Walking, cycling, or driving modes.
Multiple contours per call (e.g., 10, 20, 30 minutes).
Composes with search_places to find what's reachable, and with predict to anchor a probability surface.

Built for

For public-safety GIS For SAR teams For integrators

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_isochrone

"How far can I cycle in 15 minutes from Liverpool Street?"

claude_desktop_config.json

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

Related capabilities.

get_matrix

An N-by-M travel-time matrix between sources and destinations. The basis for assignment, dispatch, and ETA quotes.

get_directions

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

search_places

Points of interest near a location, by category or by venue name. Sorted by distance.

Ready to call it?

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

Get an API key See the REST endpoint