# Lviv Public Transport MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-vbhjckfd-timetable-api-node
- Repository: https://github.com/vbhjckfd/timetable-api-node
- Website: https://lad.lviv.ua

## Install
- Endpoint: https://api.lad.lviv.ua/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://api.lad.lviv.ua/mcp

## Tools
- get_stop_realtime (Get Stop Realtime) - 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. Endpoint: https://api.lad.lviv.ua/mcp
- get_route_static (Get Route Static) - 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. 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. Endpoint: https://api.lad.lviv.ua/mcp
- get_route_realtime (Get Route Realtime) - 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. Endpoint: https://api.lad.lviv.ua/mcp
- get_stop_geometry (Get Stop Geometry) - 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. Endpoint: https://api.lad.lviv.ua/mcp
- get_stops_around_location (Get Stops Around Location) - 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. Endpoint: https://api.lad.lviv.ua/mcp

## Resources
- timetable://about - About Lviv Timetable MCP Scope, usage, and data caveats for this server. MIME type: text/markdown
- timetable://reference/tools - Tools reference What each MCP tool returns and when to use it. MIME type: text/markdown
- timetable://reference/prompts - Prompts reference Catalog of prompt templates (EN/UA) and their arguments. MIME type: text/markdown

## Prompts
- transit-map-view - Transit Map View Render live vehicles on map for a stop. Arguments: stop_id
- transit-arrival-list - Transit Arrival List Render upcoming arrivals list for a stop. Arguments: stop_id
- transit-hybrid-view - Transit Hybrid View Render map and arrival list together with synchronized ETA values. Arguments: stop_id

## Metadata
- Owner: io.github.vbhjckfd
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Apr 26, 2026
- Source: https://registry.modelcontextprotocol.io