Skip to main content
Glama
Sign In
oebb-mcp-server

oebb-mcp-server

by slettmayer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

oebb-mcp-server

PyPI Python License: MIT

MCP server for OeBB (Austrian Federal Railways) train data. Query Austrian train stations, departures, connections, and service alerts directly from LLMs via the Model Context Protocol.

Installation

Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "oebb": {
      "command": "uvx",
      "args": ["oebb-mcp-server"]
    }
  }
}

Claude Code

claude mcp add oebb -- uvx oebb-mcp-server

From source (development)

{
  "mcpServers": {
    "oebb": {
      "command": "uvx",
      "args": ["--from", "/path/to/oebb-mcp-server", "oebb-mcp-server"]
    }
  }
}

Related MCP server: swiss-public-transport-mcp

Tools

search_station

Search OeBB stations by name. Returns matching stations with IDs, coordinates, and types.

Parameter

Type

Default

Description

query

string

required

Station name (e.g. "Wien Hbf")

max_results

int

10

Maximum results

station_board

Fetch live departures or arrivals at a station. Provide either station_id or station_name.

Parameter

Type

Default

Description

station_id

string

—

OeBB station ID (e.g. "1190100")

station_name

string

—

Station name (auto-resolved)

board_type

string

"DEP"

"DEP" for departures, "ARR" for arrivals

max_journeys

int

10

Maximum journeys

trip_search

Search train connections between two stations. Supports time planning and direct-only filtering.

Parameter

Type

Default

Description

from_station_id

string

—

Departure station ID

from_station_name

string

—

Departure station name

to_station_id

string

—

Arrival station ID

to_station_name

string

—

Arrival station name

max_connections

int

5

Maximum connections

time

string

now

ISO 8601 time (e.g. "2026-04-15T08:00:00")

time_mode

string

"departure"

"departure" or "arrival"

direct_only

bool

false

Only direct connections

service_alerts

Fetch current OeBB service alerts and disruptions.

Parameter

Type

Default

Description

max_alerts

int

20

Maximum alerts

product_filter

int

65535

Product bitmask (1=ICE/RJX, 2=IC/EC, 4=NJ, 8=D/EN, 16=REX/R, 32=S-Bahn, 64=Bus, 128=Ferry, 256=U-Bahn, 512=Tram, 4096=private operators like Westbahn/RegioJet, 65535=all)

Development

# Install dependencies
uv sync

# Lint & format
ruff check .
ruff format .

# Run unit tests
pytest tests/ -v -m "not integration"

# Run integration tests (hits real OeBB API)
pytest tests/ -v -m integration

License

MIT

Available Tools

4 tools
search_stationA

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)

Inputs: query (required), max_results. Returns: result

service_alertsA

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

Inputs: max_alerts, product_filter. Returns: result

station_boardA

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)

Inputs: board_type, station_id, max_journeys, station_name. Returns: result

trip_searchA

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)

Inputs: time, time_mode, direct_only, to_station_id, +4 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct domain action: searching stations, retrieving station boards, planning trips, and fetching service alerts. There is no functional overlap between them.

    Naming Consistency3/5

    Names use snake_case consistently but mix word orders: 'search_station' is verb_noun, 'station_board' is noun_noun, 'trip_search' is noun_verb, and 'service_alerts' is noun_noun. This makes the pattern less predictable, though still readable.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped to the core use cases of a railway information service: station lookup, live board, journey planning, and alerts. Each tool earns its place.

    Completeness5/5

    The surface covers the essential needs: finding stations, viewing live departures/arrivals, planning trips with advanced options, and checking disruptions. No obvious dead ends or missing operations for its stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers