Rhein-Ruhr Fahrplan MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add rhein-ruhr-fahrplan-mcp -- uvx rhein-ruhr-fahrplan-mcp

{
  "mcpServers": {
    "rhein-ruhr-fahrplan-mcp": {
      "command": "uvx",
      "args": [
        "rhein-ruhr-fahrplan-mcp"
      ]
    }
  }
}

[mcp_servers.rhein-ruhr-fahrplan-mcp]
command = "uvx"
args = ["rhein-ruhr-fahrplan-mcp"]

{
  "mcpServers": {
    "rhein-ruhr-fahrplan-mcp": {
      "command": "uvx",
      "args": [
        "rhein-ruhr-fahrplan-mcp"
      ]
    }
  }
}

{
  "servers": {
    "rhein-ruhr-fahrplan-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "rhein-ruhr-fahrplan-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: FAHRPLAN_AGENCY_IDS (Comma-separated GTFS agency IDs to enable the schedule database (e.g. 'nia-25'). Without it the server runs live-only; schedule tools return a configuration hint. An unfiltered import would create a ~500 MB database and is intentionally not the default), FAHRPLAN_OPERATOR (Optional: filter live departures/arrivals by operator code (e.g. 'NIAG'). Empty = all operators), FAHRPLAN_DEFAULT_START (Optional: default start stop (DHID like 'de:05154:35739', EFA ID or unique name), available via the get_default_start tool).