Lombardia Trains vs OeBB (Austrian Railwa… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Lombardia Trains vs OeBB (Austrian Railways)
In-depth architectural comparison of the Lombardia Trains and OeBB (Austrian Railways) MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Lombardia Trains
Travel & Transportation · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
OeBB (Austrian Railways)
Travel & Transportation · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Lombardia Trains if you need specialized Travel & Transportation tools running via a local process. Choose OeBB (Austrian Railways) if your workspace requires Travel & Transportation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Lombardia Trains when:
You need dedicated capabilities in the Travel & Transportation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Lombardia Trains is categorized under Travel & Transportation and uses a local stdio subprocess. In contrast, OeBB (Austrian Railways) belongs to Travel & Transportation using local stdio subprocess. Select Lombardia Trains when you need capabilities focused on travel & transportation and OeBB (Austrian Railways) when you require tools for travel & transportation.
"where is train 4307 right now, and how late is it?"
OeBB (Austrian Railways) Tools (4)
search_station
Search OeBB stations by name.
Use this to find station IDs needed for other tools.
Returns matching stations with IDs, coordinates, and types.
Args:
query: Station name to search for (e.g. "Wien Hbf", "Salzburg")
max_results: Maximum number of results to return (default 10)
station_board
Fetch live departures or arrivals at an OeBB station.
Provide either station_id or station_name (name is auto-resolved).
Returns train products, directions, planned/real times, and platforms.
Args:
station_id: OeBB station ID (e.g. "1190100" for Wien Hbf)
station_name: Station name to search for (e.g. "Wien Hbf")
board_type: "DEP" for departures (default), "ARR" for arrivals
max_journeys: Maximum number of journeys to return (default 10)
trip_search
Search train connections between two OeBB stations.
Provide station IDs or names for departure and arrival stations.
Supports future trip planning via time/time_mode parameters.
Returns connections with departure/arrival times, duration, changes, and legs.
Args:
from_station_id: Departure station ID (e.g. "1190100")
from_station_name: Departure station name (e.g. "Wien Hbf")
to_station_id: Arrival station ID (e.g. "8100002")
to_station_name: Arrival station name (e.g. "Salzburg Hbf")
max_connections: Maximum connections to return (default 5)
time: ISO 8601 time (e.g. "2026-04-15T08:00:00"), defaults to now
time_mode: "departure" (default) or "arrival"
direct_only: Only show direct connections without changes (default false)
service_alerts
Fetch current OeBB service alerts and disruptions.
Returns active alerts with headlines, descriptions, affected stations,
and date ranges.
Args:
max_alerts: Maximum number of alerts to return (default 20)
product_filter: Product bitmask — 1=ICE/RJX, 2=IC/EC, 4=NJ,
8=D/EN, 16=REX/R, 32=S-Bahn, 64=Bus,
4096=private operators (Westbahn/RegioJet), 65535=all