ÖBB MCP server: let your AI agent search Austrian train and bus connections
Wield is an MCP server that gives your AI agent one ÖBB tool, oebb.at/search-connections. The tool finds train and bus connections between two stations or places on a date. It returns departure and arrival times, live times where ÖBB knows them, changes, platforms, duration and each leg's line. It runs in your own browser. The result has no ticket prices.
ÖBB Scotty Find train and bus connections in Austria (ÖBB Scotty)
Read-only, no loginFailed the last daily check
Parameters (6)
What your agent gets
| Recipe | What it does | Login | Status (7 Nov 2026) |
|---|---|---|---|
oebb.at/search-connections | Connections between two stations or places in Austria and beyond, by departure or arrival time, with changes, platforms and cancelled trips | No | OK, 7 of 7 checks, 2 requests, about 2.6 s |
The tool takes from, to and date (YYYY-MM-DD). It also takes time (HH:MM, Austrian local time, default 08:00), arrive_by (true to read time as the latest arrival) and results (default 5). Station names are free text. The tool uses the first match of ÖBB's station search and returns the station it used, so your agent can check it.
In our check on 7 November 2026, a search from Wien Hbf to Salzburg Hbf on 14 January, departing at 08:00, passed 7 of 7 checks with 2 requests in 2.6 seconds. A run has no model in the loop, so it uses no LLM tokens. Wield is the layer your agent calls. It is not an agent itself.
How a request flows
- You ask your agent: "Find trains from Wien Hbf to Graz Hbf on 20 November 2026, from 09:00, and show changes and platforms."
- The agent calls
find_recipe, thenrunwithoebb.at/search-connectionsand the parameters. wield-mcppasses the run through the local bridge to the Wield extension.- The extension sends the two requests from your browser to ÖBB's journey planner.
- The connections go back to your agent. Nothing passes through wield.run.
What leaves your computer
The only host is fahrplan.oebb.at. A search makes two read-only requests to the planner's own gateway, the same requests the Scotty journey planner makes when you search it yourself. The recipe needs no login. Wield logs each request on your computer only: method, host, path, status and timing. It never logs bodies or query values. Telemetry is off by default. Wield never reads, copies or sends your cookies or passwords.
ÖBB's terms, in plain words
We have not reviewed ÖBB's terms for automated access yet, so this is not legal advice. One run is one person's search, with two read-only requests. The recipe does not buy tickets and does not collect timetables in bulk. Check the site's terms yourself before you automate anything more.
Limits and what is not working yet
- Read only. The recipe finds connections. It shows no prices and does not buy tickets. Tickets are sold in the ÖBB shop.
- Stations are matched, not confirmed. The first match wins, so check
fromandtoin the result. - Timetable period. A date outside the timetable period returns no connections. The result then carries the planner's own message, which gives the valid period.
- Run limits apply. A run has at most 12 steps, 40 requests, 5 MB per response and 60 seconds.
FAQ
Does the tool show ticket prices?
No. The result has no prices. Open the ÖBB shop to buy a ticket.
Which AI apps work with it?
Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. Other MCP clients work with the standard stdio config. See the install page.
Does it need an ÖBB login?
No. The search works without an account.
Does it cover trips beyond Austria?
Yes, the recipe takes places in Austria and beyond. ÖBB's station search picks the station, and the result shows which one it used.
How does it compare with a browser agent?
We have not benchmarked this recipe yet, so this page makes no speed or success comparison.