traveltime_time_filter

Pack: traveltime · Endpoint: https://gateway.pipeworx.io/traveltime/mcp

Which of these locations are reachable within N minutes from an origin by public transport (or driving/walking/cycling), and how long each takes. Filters candidate destinations by travel time. Example: traveltime_time_filter({ origin_lat: 51.5072, origin_lon: -0.1276, destinations: [{ id: “a”, lat: 51.52, lon: -0.09 }, { id: “b”, lat: 51.60, lon: -0.20 }], travel_time: 45, minutes: true, transport: “public_transport”, departure_time: “2026-07-06T08:30:00Z”, _apiKey: “appId:apiKey” })

Parameters

NameTypeRequiredDescription
origin_latnumbernoOrigin latitude
origin_lonnumbernoOrigin longitude
destinationsarraynoCandidate destinations to test. Each: { id?, lat, lon }. Max 2000. IDs auto-generated (“dest_0”, …) if omitted.
Eachunknownno
itemsobjectno
propertiesstringno
idstringno
latnumberyes
lonnumberyes
travel_timenumbernoMax journey time. Seconds by default (default 1800 = 30 min). Set minutes:true to pass minutes. Max 14400s / 240 min.
minutesbooleannoIf true, travel_time is interpreted as minutes and multiplied by 60.
transportstringnoTransport mode (default “public_transport”). One of: driving, walking, cycling, public_transport, driving+public_transport.
departure_timestringnoISO 8601 departure timestamp (e.g. “2026-07-06T08:30:00Z”). Public-transport searches need a timestamp; defaults to now if omitted.
_apiKeystringnoTravelTime credentials as “appId:apiKey” from your traveltime.com account.

Example call

curl -X POST https://gateway.pipeworx.io/traveltime/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"traveltime_time_filter","arguments":{}}}'

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "traveltime": {
      "url": "https://gateway.pipeworx.io/traveltime/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build July 4, 2026