Summary
Each mode keeps its own identifiers, so a trip across two of them is two lookups joined by hand.
İZBAN works from station IDs, ESHOT from durakId and hatNo, trams from a seferId, ferries from iskeleId and gunId, and nothing here routes across modes — an agent planning bus to train resolves each leg separately. What the live layer does give you is position rather than promise: get-line-bus-locations and the two approaching-bus tools report where vehicles actually are, which is a different question from what the timetable says.
What it is
A client for İzmir's municipal transport data, with 19 tools spanning the İZBAN suburban railway, ESHOT buses, the metro, the tram network, train stations and ferries.
What you get
- İZBAN: get-izban-stations for the station list with IDs, get-izban-departures between two stations, and get-izban-fare-tariff, which factors in transfer status and HTT card usage.
- ESHOT search: get-eshot-stations by name or address, get-eshot-lines by number or name, and get-nearby-stations-by-coords with inCoordSys and outCoordSys for whichever coordinate system you are working in.
- Live bus positions: get-line-bus-locations for every bus on a line, get-line-approaching-buses for one line at one stop, and get-station-approaching-buses for everything approaching a stop.
- Metro and tram: get-metro-stations with order and location data, get-metro-sefer-frequencies, get-tram-lines, get-tram-stations-by-sefer-id and get-tram-sefer-frequency-by-sefer-id.
- Ferries: get-ferry-piers covering ferry and car-ferry piers, get-ferry-working-days, get-ferry-timetables by departure, arrival and day type, and get-ferry-timetables-by-pier.
- get-train-stations for the city's gar locations with their info.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx izmir-mcp