Directions from A to B, by name.
Geocode both ends and compute the route in one call. The agent says 'how do I get from Kings Cross to Tower Bridge'. The tool handles the rest.
mcp.footstep.ai / find_and_routeWhy your agent needs this.
When the user says 'directions from Kings Cross to Tower Bridge', the agent shouldn't need to know it has to geocode first. find_and_route is the agent-native tool: pass two strings (or coordinates, or any mix), get back the route plus the matched start and end. The agent never orchestrates a multi-step flow.
This tool bundles Geocoding + Routing in a single call.
What your agent gets back.
- Origin and destination accept lat/lon OR a place name, postcode, or free-text address.
- Single tool call, single render envelope: LineString for the route plus Point layers for the matched ends.
- Same terrain block as get_directions, ready for 'is this hilly?' follow-ups.
- Reach for this on 'route from A to B' / 'directions from A to B' / 'take me from A to B' asks.
- Composes with compare_routes when the user wants mode comparison too.
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.
"Directions to the nearest train station from here."{
"mcpServers": {
"footstep": {
"url": "https://mcp.footstep.ai",
"headers": {
"x-api-key": "sk_live_your_key_here"
}
}
}
}Related capabilities.
get_directionsPoint-to-point or multi-stop routes with terrain analytics. Answer 'is this walkable?' without a second call.
geocodeTurn an address, landmark, or place name into coordinates. Returns ranked candidates with confidence scores.
compare_routesRun multiple travel modes through the same A to B and get a side-by-side comparison plus a natural-language summary.
Ready to call it?
£5 free credit on signup. One auth header, every major runtime.