Lviv Public Transport

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Lviv public transport MCP: stops, timetables, routes, and live vehicle positions. No API key.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Lviv Public Transport": {
      "url": "https://api.lad.lviv.ua/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (9)

• get_stop_realtime read-only

  Returns live arrivals at a stop: route, destination, vehicle type, minutes until arrival, and each vehicle's position. Use this as the **default tool** when the user asks about arrivals, departures, or the next bus/tram at a specific stop. Requires a numeric stop ID (shown on stop signage); use `search_stops` when you have a stop name, or `get_stops_around_location` when you have coordinates.

  Parameters:

  • stop_id (required) — integer — Municipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string.
  • lowfloor_only — boolean — Only low-floor arrivals (step-free: wheelchairs, prams). Timetable entries without a tracked vehicle are left out, since their floor is unknown. Default false.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• search_stops read-only

  Finds stops by name (Ukrainian or English transliteration, case-insensitive, partial match) and returns each stop's numeric ID, coordinates, and the routes serving it. Use this as the **first step** when the user names a stop or landmark stop (e.g. "Опера", "Rynok", "Головний вокзал") and you need a stop ID for `get_stop_realtime` or `find_routes_between`. One name usually covers both sides of the street under different IDs; each is returned, and the `routes` list tells them apart. Use `get_stops_around_location` instead when you have coordinates rather than a name.

  Parameters:

  • query (required) — string — Stop name or part of it, e.g. "Ринок", "opera", "Стрийська".
  • limit — integer — Maximum stops to return (1–25, default 10).

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• find_routes_between read-only

  Lists the routes from one place to another: which stop to board, where to get off, the direction's destination, stops in between, and the walk at each end — best first, walking counted. Each end is a stop ID (`from_stop_id`) or coordinates (`from_lat` + `from_lng`), e.g. an address the user gave; a point covers every stop within a 600 m walk of it. `options` are direct routes. `transfer_options` have exactly one interchange (never more): ride `legs[0]`, walk `transfer_walk_meters` (within a 300 m stop cluster, 0 when it is the same stop) to `legs[1].board_stop`, ride `legs[1]`. They are listed when there is no direct route or when they beat the best direct one. Every option carries `schedule`: by the timetable, when to leave, when each leg boards and alights, when you arrive, and `total_minutes` door to door. Plan for now by default, or pass `depart_at` or `arrive_by` ("HH:MM" Lviv time today, or ISO 8601). When planning for now, options also carry `next_departures`: the live next departures of the first leg from its boarding stop, so no separate `get_stop_realtime` call is needed. `map_stops` holds the best trip's stops in riding order, each with a `role` (board, transfer — or transfer_alight + transfer_board when the interchange is a walk — and alight). Use when the user asks how to get from A to B, which bus/tram goes from one place to another, how long it takes, or when to leave to be somewhere on time. A stop end covers every stop within a 300 m walk of it, since a line's two directions often stop on opposite sides of a street under different names; `board_stop` says where to actually wait. Routes the city has suspended, and stops a detour skips, are left out. `walk_meters` is set when the two ends are within a 300 m walk of each other: no ride is searched then, so tell the user to walk. Otherwise both lists empty means the trip needs two or more transfers. Get stop IDs with `search_stops` or `get_stops_around_location`.

  Parameters:

  • to_lat — number — Decimal latitude of the destination, WGS84 (e.g. 49.842 for central Lviv).
  • to_lng — number — Decimal longitude of the destination, WGS84 (e.g. 24.031 for central Lviv).
  • from_lat — number — Decimal latitude of the start point, WGS84 (e.g. 49.842 for central Lviv).
  • from_lng — number — Decimal longitude of the start point, WGS84 (e.g. 24.031 for central Lviv).
  • arrive_by — string — Arrive by this time: "HH:MM" Lviv time today, or ISO 8601. Not together with `depart_at`.
  • depart_at — string — Leave at this time: "HH:MM" Lviv time today, or ISO 8601. Default now. Not together with `arrive_by`.
  • to_stop_id — integer — Stop ID where the trip ends. Give this or `to_lat` + `to_lng`.
  • from_stop_id — integer — Stop ID where the trip starts. Give this or `from_lat` + `from_lng`.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_route_static read-only

  Returns static route data: name, long name, vehicle type, colour, the ordered stop list for both directions, and the timetable of departures from the first stop (workday, Saturday and Sunday). Use when the user asks which stops a route serves, where it goes, or its scheduled departure times. Set `include_shapes` only when you will draw the route on a map — the polylines are large and carry nothing a text answer needs. Do NOT use this for live vehicle positions — use `get_route_realtime` instead. Requires a route short name (e.g. "T30", "32A") or numeric external ID.

  Parameters:

  • route_name (required) — string — Route short name (e.g. "T30", "32A") or numeric external ID.
  • include_shapes — boolean — Include route polylines ([lat, lng] points per direction) for map drawing. Default false.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_route_realtime read-only

  Returns every vehicle currently running on a route: position, the destination it is heading to, and its next stop with estimated arrival. `headways` sums up each direction: how many vehicles run, the live gaps between consecutive vehicles in minutes (front to back), and how often the timetable says it should run right now. Use when the user asks "where is my tram/bus right now?", how many vehicles are running, how far the next one is, or how often a route runs. Pass `direction` (0 or 1, as in `get_route_static`'s `stops`) to get only one way. Prefer `get_stop_realtime` when the user is at a stop and wants arrival times there. Requires a route short name (e.g. "T30", "32A") or numeric external ID.

  Parameters:

  • route_name (required) — string — Route short name (e.g. "T30", "32A") or numeric external ID.
  • direction — integer — Only vehicles heading this way: 0 or 1, the index into get_route_static's `stops`. Omit for both.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_disruptions read-only

  Lists closures, detours and moved stops the city announced that are in force today: affected routes, the streets a detour uses, routes to take instead of a suspended one, reason, dates and source. The GTFS stop lists and timetables do not reflect any of this. Use when the user asks about road works, closures, detours, or why a route is not running or a vehicle is off its usual path. Pass `route` and/or `stop_id` to get only the entries touching them; omit both for the whole city.

  Parameters:

  • route — string — Only disruptions on this route, by short name (e.g. "Т30", "А34"). Omit for all routes.
  • stop_id — integer — Only disruptions at this stop. Omit for all stops.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_stops_around_location read-only

  Finds stops near a geographic point, returning each stop's numeric ID, name, coordinates, walking distance, and the routes serving it. Use this as the **first step** when the user gives an address or coordinates and you need stop IDs for `get_stop_realtime` or `find_routes_between`. Use `search_stops` instead when the user gives a stop name. Default radius is 1 000 m; narrow it (e.g. 300 m) for dense urban areas or widen it (up to 3 000 m) for rural locations.

  Parameters:

  • latitude (required) — number — Decimal latitude of the search centre, WGS84 (e.g. 49.842 for central Lviv).
  • longitude (required) — number — Decimal longitude of the search centre, WGS84 (e.g. 24.031 for central Lviv).
  • radius_meters — integer — Search radius in metres (50–3000, default 1000). Use ~300 for dense urban intersections, up to 3000 for suburban or rural areas.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_nearby_vehicles read-only

  Returns live vehicles near a point, nearest first, each with its route, destination, and distance. Use when the user asks "what transport is near me right now?" or wants a live map around a location. Narrow with `route` when the user cares about one line; prefer `get_route_realtime` for a whole route and `get_stop_realtime` for arrival times at a stop. Requires decimal latitude and longitude (WGS84).

  Parameters:

  • latitude (required) — number — Decimal latitude of the centre point, WGS84 (e.g. 49.842 for central Lviv).
  • longitude (required) — number — Decimal longitude of the centre point, WGS84 (e.g. 24.031 for central Lviv).
  • limit — integer — Maximum vehicles to return, nearest first (1–50, default 15). `total` reports how many were in range.
  • route — string — Only vehicles on this route, by short name (e.g. "Т30", "А1"). Omit for all routes.
  • lowfloor_only — boolean — Only low-floor vehicles (step-free: wheelchairs, prams). Timetable entries without a tracked vehicle are left out, since their floor is unknown. Default false.
  • radius_meters — integer — Search radius in metres (100–1000, default 500).

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_vehicle_info read-only

  Returns details for one vehicle by ID: position, route, destination, license plate, and its upcoming stops with names and estimated arrival times. Use when the user wants to follow a particular vehicle, e.g. "where does this tram go next?" or "when will it reach X?". Vehicle IDs come from `get_route_realtime`, `get_nearby_vehicles`, or `get_stop_realtime` results. Do NOT use this to get all vehicles on a route — use `get_route_realtime` instead.

  Parameters:

  • vehicle_id (required) — string — Vehicle ID as returned by get_route_realtime, get_nearby_vehicles, or get_stop_realtime.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.