Lviv Public Transport

Name: Lviv Public Transport
Author: vbhjckfd

作者：vbhjckfd版本 1.8.11i★ –i在云端运行

注册名称io.github.vbhjckfd/timetable-api-node

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：3 项中通过 3 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
可以做 9 件事（工具） get_stop_realtime, search_stops, find_routes_between, get_route_static …
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

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

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 vbhjckfd 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
✓ 通过
端点有响应
在 523 毫秒内响应（HTTP 200）
– 不适用
使用 OAuth 登录
无需登录
✓ 通过
工具描述中没有隐藏指令
已读取 9 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32435 个服务器的 0%
发布到注册中心的时间比此分类中其他 32435 个服务器的 94% 更新
基础检查结果等于或优于此分类中其他 32435 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Lviv Public Transport 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.8.11）于前天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Apify MCP Server

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211昨天更新

安装

Apify MCP Server

作者：apify

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分；其余内容请在仓库中阅读