Lviv Public Transport

Name: Lviv Public Transport
Author: vbhjckfd

by vbhjckfdversion 1.8.11i★ –iRuns in the cloud

Registry nameio.github.vbhjckfd/timetable-api-node

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
Can do 9 things (tools) get_stop_realtime, search_stops, find_routes_between, get_route_static …
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://api.lad.lviv.ua/mcp

Run this in your terminal

claude mcp add --transport http timetable-api-node https://api.lad.lviv.ua/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "timetable-api-node": {
      "url": "https://api.lad.lviv.ua/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "timetable-api-node": {
      "type": "http",
      "url": "https://api.lad.lviv.ua/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://api.lad.lviv.ua/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

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 sto
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", "Головний вок
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. Each end is a stop ID (`from_stop_id`) or coordinates (`from_lat` + `from_lng`), e.g. an addre
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 depa
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. `headways` sums up each direction: how many vehicles run, the live gaps between consecutive vehicles in minutes (front to back), and how often
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 as
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_betwee
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_realti
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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account vbhjckfd, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 523 ms (HTTP 200)
– Not applicable
Sign-in with OAuth
No sign-in needed
✓ Pass
No hidden instructions in tool descriptions
Read 9 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

More stars than 0% of the other 32403 servers in this category
Published to the registry more recently than 94% of the other 32403 servers in this category
Basic checks equal to or better than 100% of the other 32403 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Lviv Public Transport safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.8.11) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

LickityClick

by lickity.click

Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Timetable API Node

Express-based API for Lviv transport timetable data with a read-only MCP endpoint.

Requirements

Node.js 26 (see .nvmrc)

Run locally

nvm use

npm install cp .env.dist .env make import # first run, and whenever the GTFS feed changes make start

make import downloads the static GTFS feed (gtfs-import-config.json) and writes the two stores the server reads: database/Timetable (LokiJS: stops, routes, shapes, first-stop schedules) and database/gtfs (SQLite: trips and calendars). Both are gitignored, so a fresh clone has no data until it runs. make import-slim re-imports only the light tables into SQLite and leaves database/Timetable alone.

Configuration

All variables are optional; see .env.dist.

Variable	Default	Purpose
`PORT`	`8080`	HTTP port.
`VEHICLES_LOCATION_URL`	`https://track.ua-gis.com/gtfs/lviv/vehicle_position`	GTFS-RT vehicle positions feed.
`TRIP_UDPDATES_URL`	`https://track.ua-gis.com/gtfs/lviv/trip_updates`	GTFS-RT trip updates feed (the misspelling is the real name).
`MCP_PUBLIC_BASE_URL`	`https://api.lad.lviv.ua`	Base URL used in MCP metadata (icon URL).
`NEW_RELIC_LICENSE_KEY`	—	Enables New Relic APM (see Monitoring).
`NEW_RELIC_APP_NAME`, `NEW_RELIC_LOG_LEVEL`	`timetable-api-node`, `info`	New Relic agent settings.
`PULSE_WORKER_URL`, `PULSE_SIGNAL_SECRET`	—	Signal a Pulse worker on each `/stops/:code/timetable` request; both must be set.
`MCP_URL`	`https://api.lad.lviv.ua/mcp`	Only for the `timetable-mcp` stdio proxy: the remote endpoint it forwards to.

Test

nvm use && make test

TypeScript

The code is TypeScript and runs straight from the .ts sources under Node's built-in type stripping — there is no build step for the server, the GTFS import or the scripts. That means only erasable syntax (no enum, namespace or parameter properties), import type for type-only imports, and relative imports that name the .ts file; tsconfig.json enforces all three.

npm run typecheck   # tsc, no emit

npm run build emits just mcp/stdio.js, the published bin: Node does not strip types inside node_modules, so the npm package has to ship JavaScript. It runs on npm pack/npm publish; the output is not committed.

public/stopOverrides.js is served to browsers as-is, so it stays JavaScript and is type-checked from its JSDoc.

Monitoring

New Relic APM, off unless NEW_RELIC_LICENSE_KEY is set. It also carries errors and the custom metrics recorded through utils/metrics.ts.

New Relic runs as a preloaded agent, so npm start carries the flags:

node -r dotenv/config -r newrelic --import newrelic/esm-loader.mjs index.ts

dotenv/config is preloaded first so .env is populated before the agent reads its configuration. The config file is newrelic.cjs (the agent is CommonJS and this project is ESM) and holds no secrets — the key comes from the environment. /health is excluded from transactions via rules.ignore.

The account is in the EU region; its license key starts with eu01xx and the agent picks the collector from that prefix. Use the 40-character ingest license key, not an NRAK-... user API key.

Cloud Run reads the key from Secret Manager:

gcloud run services update timetable-api-node --region=europe-north1 --project=timetable-252615 --set-secrets=NEW_RELIC_LICENSE_KEY=new-relic-license-key:latest

MCP Server

This service exposes a public read-only MCP endpoint over Streamable HTTP. It speaks MCP revision 2026-07-28 (stateless: server/discover, a per-request _meta envelope, cacheable list results) and still serves 2025-era clients that open with initialize (2025-11-25 back to 2024-11-05).

MCP endpoint: /mcp
Server card: /.well-known/mcp/server-card.json
Discovery hint: /robots.txt (non-standard comment hint)

Production deployment (see cloudbuild.yaml for Cloud Run) serves REST and MCP from [api.lad.lviv.ua](https://api.lad.lviv.ua). The main site [lad.lviv.ua](https://lad.lviv.ua) is the public transport website (this repo still links there in HTML sitemap and tables for people, not for the API host). Use your own origin when running locally.

LLM and `/mcp` flow

An MCP client (Claude, Cursor, or the MCP SDK) talks JSON-RPC over Streamable HTTP to POST /mcp. Tool handlers reuse the same Express actions as the REST API, backed by LokiJS timetable data, GTFS SQLite (via gtfs), and live GTFS-RT feeds (for example track.ua-gis.com).

graph LR;

Client[LLM or MCP client] -->|JSON-RPC Streamable HTTP| Mcp["POST /mcp"]; Mcp --> Tools[Tool handlers]; Tools --> Actions[Express actions]; Actions --> Loki[(LokiJS)]; Actions --> Gtfs[(GTFS SQLite)]; Actions --> Rt[GTFS-RT upstream]; Loki --> Actions; Gtfs --> Actions; Rt --> Actions; Actions --> Tools; Tools --> Mcp; Mcp -->|MCP tool result| Client;

Try the live API

MCP Inspector (local): run npx @modelcontextprotocol/inspector, then open the UI with transport and server URL prefilled (from the inspector README):

http://localhost:6274/?transport=streamable-http&serverUrl=https%3A%2F%2Fapi.lad.lviv.ua%2Fmcp

Postman / curl: call a tool on production

POST https://api.lad.lviv.ua/mcp with Content-Type: application/json and Accept: application/json, text/event-stream — the Streamable HTTP transport rejects a request that does not accept both. The server is stateless: there is no session, so tools/call works on its own without an initialize first. The response arrives as a single SSE event: message frame carrying the JSON-RPC result. This is the 2025-era request shape; a 2026-07-28 request also sends MCP-Protocol-Version: 2026-07-28 and Mcp-Method headers, plus io.modelcontextprotocol/protocolVersion and io.modelcontextprotocol/clientCapabilities in params._meta.

curl -s https://api.lad.lviv.ua/mcp \

-H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_stop_realtime","arguments":{"stop_id":101}}}'

Example `tools/call` body shape:

"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get_stop_realtime", "arguments": { "stop_id": 101 } } }

Successful tool responses return a natural-language text summary inside MCP content items (type: "text") — e.g. *"Stop «Площа Ринок»: 6 arrivals. Next: Т02 → «Пасічна» in 3 min."* The full structured payload is in the structuredContent field (for schema-aware clients). Each structuredContent payload follows one contract:

"view": "transit_realtime", "data": { "...": "tool-specific payload" }, "ui_blocks": [ { "type": "map", "data": { "center": [49.84, 24.03], "zoom": 14, "layers": { "stops": "data.stop", "vehicles": "data.arrivals" } } }, { "type": "arrival_list", "data": { "source": "data.arrivals" } } ] }

ui_blocks point into data instead of repeating it. A map block gives the centre and zoom, and layers maps stops, vehicles and polylines to a dot path in the result; every stop and vehicle there has lat/lng, vehicles also bearing. An arrival_list block names the arrivals array to render, already sorted by arrival_minutes (null = no ETA).

Exposed tools

All tools are read-only. Stop IDs are the numeric codes on stop signs, returned as strings ("707"). Route names are the short names on vehicles ("Т30", "А1"); Latin "T30"/"A01" work too, and a bare number is read as an internal route ID. An unknown route or vehicle returns isError: true with a hint on what to pass instead.

Tool	Arguments	Returns
`search_stops`	`query` (string, ≥ 2 chars), `limit` (1–25, default 10)	Stops whose Ukrainian or English name contains every query word (inflection-tolerant: `"опера"` finds «Театр опери та балету»; punctuation and Latin look-alike letters are ignored, so `"пл. ринок"` and `"Cихiв"` match), with `routes`.
`get_stops_around_location`	`latitude`, `longitude`, `radius_meters` (50–3000, default 1000)	Stops near a point, nearest first, with `distance_meters` and `routes`.
`get_stop_realtime`	`stop_id`, `lowfloor_only` (default false)	Live arrivals: `route`, `direction` (destination), `vehicle_type`, `arrival_minutes`, vehicle position, `lowfloor`; `scheduled: true` marks timetable entries shown when no vehicle is predicted.
`find_routes_between`	`from_stop_id` or `from_lat` + `from_lng`; `to_stop_id` or `to_lat` + `to_lng`; `depart_at` or `arrive_by` (`"HH:MM"` Lviv time or ISO 8601, default now)	Routes within a 300 m walk of each stop end (600 m of a point), best first: direct `options` (`board_stop`, `alight_stop`, `destination`, `stops_count`, walk at each end) and `transfer_options` with exactly one interchange inside a 300 m stop cluster. Each option carries `schedule` (timetable estimate: `leave_at`, per-leg `board_at`/`alight_at`, `arrive_at`, `total_minutes`) and, when planning for now, `next_departures` (live, from the boarding stop). Suspended routes and stops a detour skips are left out; `walk_meters` when the ends are a short walk apart.
`get_route_static`	`route_name`, `include_shapes` (default false)	Name, type, colour, stop lists for both directions, first-stop timetable; polylines only on request.
`get_route_realtime`	`route_name`, `direction` (0 or 1, optional)	Vehicles on the route with `destination` and `next_stop` (`id`, `name`, ISO `arrival`); `headways` per direction: vehicle count, live `gaps_minutes` front to back, `scheduled_headway_minutes`.
`get_nearby_vehicles`	`latitude`, `longitude`, `radius_meters` (100–1000, default 500), `route`, `limit` (1–50, default 15), `lowfloor_only` (default false)	Live vehicles nearest first, with `destination` and `distance_meters`; `total` counts all in range.

| get_vehicle_info | vehicle_id | One vehicle: position, route, destination, plate, upcoming stops (id, name, ISO

Only the beginning is shown; read the rest in the repo

Lviv Public Transport

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

LickityClick

README from the maker

Timetable API Node

Requirements

Run locally

Configuration

Test

TypeScript

Monitoring

MCP Server

LLM and /mcp flow

Try the live API

Exposed tools

LLM and `/mcp` flow