# Lviv Public Transport

- Registry name: `io.github.vbhjckfd/timetable-api-node` · version 1.8.0
- Categories (automatic, keyword rules): Maps, location & weather
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): completions, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.vbhjckfd%2Ftimetable-api-node
- Server page: https://mcpstation.net/s/io.github.vbhjckfd--timetable-api-node.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://api.lad.lviv.ua/mcp`

## Tools (as reported by the server, not verified)

- `get\_stop\_realtime`: 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 \`sea
- `search\_stops`: 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
- `find\_routes\_between`: 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 \`t
- `get\_route\_static`: 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 \`in
- `get\_route\_realtime`: 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 a
- `get\_disruptions`: 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,
- `get\_stops\_around\_location`: 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\_stop
- `get\_nearby\_vehicles`: 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 rout
- `get\_vehicle\_info`: 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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html