mcp server
Lviv Public Transport
Lviv public transport MCP: stops, timetables, routes, and live vehicle positions. No API key.
Description as published by the maintainer. Source
- version 1.3.4
- active
active — Registry entry last updated 2026-06-22.
What this server can do
7 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_nearby_vehicles(latitude, longitude)- Returns live positions for all transit vehicles within 1 km of given coordinates. Use when the user asks 'what transport is near me?' or wants a live map of all vehicles around a location without knowing the route. Prefer `get_route_realtime` when a specific route is already known. Requires decimal latitude and longitude (WGS84); use `get_stops_around_location` first if you only have a stop name. Required: latitude, longitude.
get_route_realtime(route_name)- Returns live positions for all vehicles currently running on a route, optimised for map rendering. Use when the user asks "where is my tram/bus right now?" or wants to see all active vehicles on a specific route on a map. Prefer `get_stop_realtime` when the user is at a stop and wants to know arrival times rather than vehicle positions. Prefer `get_route_static` when only the route shape or stop list is needed without live data. Requires a route short name (e.g. "T30", "32A") or numeric external ID. Required: route_name.
get_route_static(route_name)- Returns static route metadata: short and long name, vehicle type, brand colour, ordered stop lists for both directions, and route polylines (shapes) for map rendering. Use when the user asks which stops a route serves, what a route looks like on a map, or what the scheduled departure times are (workday and weekend schedules are included in each stop's `schedule` field). Do NOT use this when live vehicle positions are needed — use `get_route_realtime` instead. Requires a route short name (e.g. "T30", "32A") or numeric external ID; call `get_stops_around_location` first if you only know a location and need to discover which routes serve it. Required: route_name.
get_stop_geometry(stop_id)- Returns static map context for a stop: its marker and polylines for every route that serves it. No live data is fetched. Use this when you need to enrich an existing map with route shapes (e.g. overlay polylines alongside a `get_stop_realtime` map block) or when the user asks to visualise which routes pass a stop without needing live arrivals. Do NOT use this when live arrival times or vehicle positions are needed — use `get_stop_realtime` instead. Requires a numeric stop ID; call `get_stops_around_location` first if you only have coordinates. Required: stop_id.
get_stop_realtime(stop_id)- Returns live arrivals and vehicle positions for a stop, producing both a map UI block and a structured arrival list. Use this as the **default tool** when the user asks about arrivals, departures, or vehicles at a specific stop. Prefer `get_stop_geometry` when only static route polylines are needed and live data is irrelevant. Requires a numeric stop ID (shown on stop signage); use `get_stops_around_location` first if you only have an address or coordinates. Required: stop_id.
get_stops_around_location(latitude, longitude, radius_meters)- Discovers transit stops near a geographic point, returning each stop's numeric code, name, coordinates, and walking distance. Also emits a map UI block with multiple markers for map-capable clients (e.g. ChatGPT). Use this as the **first step** whenever the user provides an address, place name, or coordinates and you need stop IDs before calling `get_stop_realtime` or `get_stop_geometry`. Do NOT use this to fetch arrivals or live vehicle data — it returns stop metadata only. 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. Required: latitude, longitude.
get_vehicle_info(vehicle_id)- Returns full details for a specific transit vehicle by its ID: current position, bearing, route, license plate, direction, and upcoming stop arrivals. Use when the user wants to track a particular vehicle (e.g. after seeing it on a `get_route_realtime` map). 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. Required: vehicle_id.
Last successful function declaration observed on . Source: https://api.lad.lviv.ua/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.lad.lviv.ua/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.3.4 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-22 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-22 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 7 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.lad.lviv.ua | |
| mcp endpoint status | ok | The server listed 7 functions when asked. | as of probe | api.lad.lviv.ua |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json