poland-transit-mcp
An MCP server for getting around Polish cities: places, walking routes, timetables and door-to-door trip plans.
Built on OpenStreetMap and the operators' official GTFS timetables. Every answer names its sources and data dates.
What it does
- Finds places: attractions, museums, parks, stations, stops, hotels and streets, by name or near a point.
- Walks: routes along mapped streets and paths that never cross water except on a bridge.
- Reads timetables: departures and lines from each operator's GTFS feed, live estimates in Gdańsk (opt-in).
- Plans trips: up to 3 door-to-door options, leaving at or arriving by a time, also between cities by train or FlixBus.
- Draws maps: a PNG of an area or of a planned trip.
- Answers lean and typed: every tool declares its answer shape (
outputSchema);detail: "full"adds what only code needs.
Cities and data
| Cities | Warszawa · Kraków · Katowice (GZM) · Wrocław · Poznań · Gdańsk · Lublin · Toruń · Zakopane |
| Between cities | poland: trains of 13 rail operators and FlixBus coaches |
| Data | one SQLite file per city, built by you from the official sources (not in git; no prebuilt download yet) |
Quick start
Needs uv, osmium-tool and a Rust toolchain (macOS: brew install uv osmium-tool rust).
No Rust? Leave out --extra fast: the built-in Python search gives the same answers, more slowly.
git clone https://github.com/alexratmanpl/poland-transit-mcp.git && cd poland-transit-mcp
uv sync --extra dev --extra fast # --extra fast: the optional Rust engine
uv run poland-transit-mcp build gdansk --download # about 2 min; writes data/cities/gdansk.sqlite
uv run python scripts/smoke.py # expect: PASS
claude mcp add poland-transit -- "$PWD/.venv/bin/poland-transit-mcp" --cities gdansk --data-dir "$PWD/data/cities" --no-download
More cities, trips between cities, other MCP clients, memory, every flag and troubleshooting: AGENTS.md.
Tools
| Tool | Answers |
|---|---|
list_cities |
cities and national layers, their features and timetable dates |
find_places |
places by name or near a point |
stops_near |
stops by walking time, with the lines serving each |
departures |
the next departures from a stop; with to, only the runs that go on to another stop |
line_info |
a line's stops, first and last run and frequency; on poland, a train |
walk_route |
a walking route between two points |
plan_trip |
door-to-door itineraries; with to_city, between cities |
plan_stations |
trains and coaches between stations, for a caller that brings the traveller to a station |
map_extract |
map geometry of an area, for code that draws its own map |
render_map |
a map picture of an area or of a planned trip |
credits |
the full credit and licence text of each data source |
Arguments, declared answer fields, errors and answer sizes: docs/TOOLS.md.
Serving it to others?
--httphas no authentication, rate limit or time limit per call: put it behind a gateway or a buffering reverse proxy (SECURITY.md). Cutting a model client's token cost with "code mode": SECURITY.md.
Documentation
| AGENTS.md | from an empty machine to a working MCP server; code map, troubleshooting, flags |
| docs/TOOLS.md | every tool: arguments, answer fields (outputSchema), lean-by-default rule, errors, sizes |
| docs/ENGINE.md | the optional Rust engine: why, how fast, how to install |
| docs/INTERCITY.md | trips between cities: how they are planned, measurements, limits |
| docs/SCALING.md | what each city costs, memory budget, what runs on what hardware |
| docs/OBSERVABILITY.md | opt-in OpenTelemetry traces and metrics |
| docs/CHECKS.md | accuracy against operators' timetables, speed and memory measurements |
| docs/PUBLISHING.md | the optional PyPI step |
| SECURITY.md | what the server trusts, running it for others, reporting a vulnerability |
| SOURCES.md · DATA-LICENSE.md | every feed with its credits · data licences and redistribution |
| DECISIONS.md · CONTRIBUTING.md · CHANGELOG.md | design choices · contributing · releases |
Licence and credits
Code: MIT. City files: ODbL 1.0 (© OpenStreetMap contributors) for the map, and each timetable keeps its publisher's
terms; Zakopane's timetable and poland are not cleared for redistribution (DATA-LICENSE.md).
Timetables from the cities' transport authorities, PKP PLK, Koleje Mazowieckie and FlixBus; GTFS conversions by
Mikołaj Kuranowski (full credits).
Metadata
Release files for poland-transit-mcp 0.5.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| poland_transit_mcp-0.5.5.tar.gz | 497.0 kB | Without provenance | Details for poland_transit_mcp-0.5.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| poland_transit_mcp-0.5.5-py3-none-any.whl | Python 3 | none | any | Details for poland_transit_mcp-0.5.5-py3-none-any.whl |
Total release size: 643.1 kB
Release files / poland_transit_mcp-0.5.5.tar.gz
| Download URL | poland_transit_mcp-0.5.5.tar.gz |
|---|---|
| Size | 497.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf9bcf049b12ad8839b6bc2b4342e16cfda411f86a83a100ee98c5883e95e5d2
|
|
BLAKE2b-256 checksum How to use checksums |
7be49d5440bce1f2c06b98ba289c238c73a3603e28832a8f16767c5bf35fc87b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.18 {"installer":{"name":"uv","version":"0.11.18","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / poland_transit_mcp-0.5.5-py3-none-any.whl
| Download URL | poland_transit_mcp-0.5.5-py3-none-any.whl |
|---|---|
| Size | 146.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e2877b3f9bace600623c741339b5cffa7f64f31aa12587b214693f41f3f4ae8
|
|
BLAKE2b-256 checksum How to use checksums |
6fd222e5dfd730123683fabd810c6dda708dfb83c67bbafbc5ef5db17c59649b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.18 {"installer":{"name":"uv","version":"0.11.18","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for poland-transit-mcp 0.5.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.