Hosted MCP server · #40 most used on Smithery

lad-lviv-ua

vbhjckfd/lad-lviv-ua

Lviv (Ukraine) public transport MCP server — live arrivals, vehicle positions, stop discovery, route shapes, and static timetables. No API key required.

Uses
9.8k
Tools
8
Runs
Hosted
Prompts
5
Listed
6mo ago

Get started

Add it to your agent

npx -y @smithery/cli@latest install vbhjckfd/lad-lviv-ua --client claude

Swap --client claude for cursor, vscode, windsurf or another client. The CLI asks for any required settings.

What it can do

8 tools

get_stop_realtime1 paramReturns live arrivals at a stop: route, destination, vehicle type, minutes until arrival, and each vehicle's position. Use this as the **…

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.

ParameterTypeDescription
stop_idintegerMunicipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string.
search_stops2 paramsFinds stops by name (Ukrainian or English transliteration, case-insensitive, partial match) and returns each stop's numeric ID, coordinat…

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_stop

ParameterTypeDescription
limitintegerMaximum stops to return (1–25, default 10).
querystringStop name or part of it, e.g. "Ринок", "opera", "Стрийська".
find_routes_between2 paramsLists the routes from one place to another: which stop to board, where to get off, the direction's destination, stops in between, and the…

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. `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

ParameterTypeDescription
to_stop_idintegerStop ID where the trip ends.
from_stop_idintegerStop ID where the trip starts.
get_route_static2 paramsReturns static route data: name, long name, vehicle type, colour, the ordered stop list for both directions, and the timetable of departu…

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.

ParameterTypeDescription
route_namestringRoute short name (e.g. "T30", "32A") or numeric external ID.
include_shapesbooleanInclude route polylines ([lat, lng] points per direction) for map drawing. Default false.
get_route_realtime1 paramReturns every vehicle currently running on a route: position, the destination it is heading to, and its next stop with estimated arrival.…

Returns every vehicle currently running on a route: position, the destination it is heading to, and its next stop with estimated arrival. Use when the user asks "where is my tram/bus right now?", how many vehicles are running, or how far the next one is. 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.

ParameterTypeDescription
route_namestringRoute short name (e.g. "T30", "32A") or numeric external ID.
get_stops_around_location3 paramsFinds stops near a geographic point, returning each stop's numeric ID, name, coordinates, walking distance, and the routes serving it. Us…

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.

ParameterTypeDescription
latitudenumberDecimal latitude of the search centre, WGS84 (e.g. 49.842 for central Lviv).
longitudenumberDecimal longitude of the search centre, WGS84 (e.g. 24.031 for central Lviv).
radius_metersintegerSearch radius in metres (50–3000, default 1000). Use ~300 for dense urban intersections, up to 3000 for suburban or rural areas.
get_nearby_vehicles5 paramsReturns live vehicles near a point, nearest first, each with its route, destination, and distance. Use when the user asks "what transport…

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).

ParameterTypeDescription
limitintegerMaximum vehicles to return, nearest first (1–50, default 15). `total` reports how many were in range.
routestringOnly vehicles on this route, by short name (e.g. "Т30", "А1"). Omit for all routes.
latitudenumberDecimal latitude of the centre point, WGS84 (e.g. 49.842 for central Lviv).
longitudenumberDecimal longitude of the centre point, WGS84 (e.g. 24.031 for central Lviv).
radius_metersintegerSearch radius in metres (100–1000, default 500).
get_vehicle_info1 paramReturns details for one vehicle by ID: position, route, destination, license plate, and its upcoming stops with names and estimated arriv…

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.

ParameterTypeDescription
vehicle_idstringVehicle ID as returned by get_route_realtime, get_nearby_vehicles, or get_stop_realtime.

Ready-made

Prompts

  • transit-map-viewRender live vehicles on map for a stop.
  • transit-arrival-listRender upcoming arrivals list for a stop.
  • transit-hybrid-viewRender map and arrival list together with synchronized ETA values.
  • plan-tripFind routes (direct or with one transfer) between two places in Lviv and the next live departures.
  • route-statusWhere the vehicles of one route are right now.

Readable data

Resources

  • aboutScope, usage, and data caveats for this server.
  • tools-referenceWhat each MCP tool returns and when to use it.
  • prompts-referenceCatalog of prompt templates and their arguments.