AnythingMCP Cloud is live — 7-day free trial−30% for 3 months with START30
AnythingMCP
Deutsche Bahn Fahrplan

Deutsche Bahn Fahrplan

German train timetable with live delays: search stations, list departures and arrivals with real-time delay, track and cancellation status, and plan journeys between any two stations. Runs on MOTIS over the open gtfs.de timetable (ICE, IC, EC, regional trains, S-Bahn) — no bahn.de scraping, no API key.

Install Deutsche on CloudAPI docs

7-day free trial · No credit card · EU-hosted

Ask Deutsche anything

Try a real prompt against Deutsche Bahn Fahrplan via AnythingMCP — Claude calls the tools, returns the answer. Press Enter on your own message to install on Cloud.

Install Deutsche on Cloud
Deutsche Bahn Fahrplan · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

Setup in 2 minutes

  1. 1Start a free trial on cloud.anythingmcp.com.
  2. 2Click Deutsche Bahn Fahrplan in the connector store. Paste credentials when prompted.
  3. 3Mint an MCP API key and point your AI client at the generated MCP URL.
Install Deutsche Bahn Fahrplan now

Guides for Deutsche

Step-by-step setup for the most popular AI clients.

Setting up Deutsche Bahn Fahrplan

From the connector definition itself: where to find the credentials, what they need to be allowed to do, and which API this adapter talks to.

This connector queries a MOTIS routing engine loaded with the open German train timetable (gtfs.de, all long-distance and regional trains incl. S-Bahn) and a live GTFS-RT feed for delays, platform changes and cancellations. AnythingMCP Cloud runs its own instance; self-hosters run the bundled motis service (deploy/motis/README.md) or point MOTIS_URL at any MOTIS. No API key.

Workflow

  1. db_search_locations turns a station name into a stop id (e.g. fv_384020). Ids change when the timetable is refreshed — resolve names in every session, never reuse ids from memory.
  2. db_get_departures / db_get_arrivals with that id for a live board; db_get_stop for the station's details.
  3. db_get_journeys with two ids plans a trip (station to station; there is no street routing, so coordinates are not accepted).

Reading the fields

  • Times are ISO 8601 in UTC (2026-09-15T13:27:00Z). Germany is UTC+1 (winter) / UTC+2 (summer) — convert before quoting a time to the user.
  • departure / arrival are the live prediction, scheduledDeparture / scheduledArrival the timetable. Delay in minutes = live − scheduled. realTime: true means the row carries live data; false means schedule only.
  • cancelled: true on a departure or leg means that stop or leg is cancelled; tripCancelled means the whole train is.
  • track is the live platform, scheduledTrack the planned one; both may be absent for smaller stops.
  • line is the train name as printed on the board (ICE 43, RE 7, S1). The free gtfs.de feed reports every train as mode REGIONAL_RAIL; tell ICE/IC/EC from regional trains by the line prefix, not by mode.

Boards: omit when for a board starting now; n is the number of rows (default 12, max 100). Big stations have many S-Bahn rows — raise n when looking for a specific long-distance train.

Journeys: time is the departure time unless arrive_by is true; omit for now. results caps the itineraries (default 4). Legs with mode: WALK are transfers.

Data: DELFI e.V. / gtfs.de (CC BY 4.0), GTFS-RT gtfs.de (CC BY-SA 4.0). Engine: MOTIS (MIT).

Your AI is two clicks away from Deutsche Bahn Fahrplan.

Install the connector, paste your credentials, ask your AI a question. 7-day free trial, no credit card.

Start free on CloudSelf-host with DockerBrowse the marketplace