Mobiliteit.lu MCP
Related Servers
Alternatives to Mobiliteit.lu MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to plan and compare walking, cycling, e-bike, Vel'OH! bike-share, and public transport journeys in Luxembourg, including hill-aware timings and live bike/dock/departure data. Provides tools for trip planning, turn-by-turn routes, place search, nearby bike-share stations, and live departures.Apache 2.0
- AlicenseAqualityDmaintenanceProvides Estonian public transport timetables, trip planning, stop search, and real-time vehicle tracking.81MIT

mcp-db-railofficial
AlicenseNot gradedqualityBmaintenanceEnables keyless access to German and European rail and public transport data, including station search, live departures and arrivals, and multi-leg journey planning with real-time updates.116 npmMIT- FlicenseNot gradedqualityDmaintenanceEnables querying Swiss public transport (trains, buses, trams, boats) for stations, connections, and station boards via the opendata.ch API.-
- AlicenseNot gradedqualityBmaintenanceEnables worldwide public transport planning through the Transitous/MOTIS API: door-to-door journeys with walking legs, departures and arrivals at stops, airport terminal stops, place search, and standalone walking routes. Results can be exported as maps and GPX files for outdoor apps.MIT
- FlicenseNot gradedqualityDmaintenanceProvides real-time Dutch Railways (NS) data for journey planning, live departures, disruptions, and station search.3-
TDQS
Scored across 2 tools
The two tools target clearly distinct actions: locating stops by coordinate versus retrieving departures for a known stop id. Their descriptions even cross-reference each other, so an agent can't confuse which to call first.
Both names use a consistent snake_case verb_noun form (find_nearby_stops, get_departures) with well-chosen verbs that match their actions.
Two tools is thin for a public transport server, which normally implies routing, lines, and schedules. The pair covers a narrow departure-board workflow but leaves the broader domain unaddressed.
Stop lookup and departures form a workable read-only core, but there's no journey planning, line/route info, or name-based stop search — notable gaps for a mobility domain.