Let Claude read live departures at a Munich MVG stop
Wield lets Claude read live departures at a Munich MVG stop. Claude runs the mvg.de/get-departures recipe with a stop name. The request runs in your own browser through the Wield extension. The result lists each line with its direction, platform and live delay. Nothing passes through wield.run.
MVG (Munich public transport) Show live departures at a Munich public transport stop
Read-only, no loginPasses the daily check
Parameters (3)
What you need
- An MCP client such as Claude Desktop, Claude Code, Cursor or Codex.
- A Chromium browser (Chrome, Edge, Brave, Arc, Vivaldi, Opera or Chromium) with the Wield extension.
- wield-mcp. Follow the quick start and the install page, then run
npx -y wield-mcp init.
You don't need an MVG account. This recipe needs no login.
Ask your agent
Ask in plain words. For example:
"What are the next 10 departures at Marienplatz? Only S-Bahn."
Claude calls find_recipe, then run with mvg.de/get-departures. It sends the stop name as station, sets limit to 10 and limits transport_types to the S-Bahn.
Params: what to put where
| Param | Required | What to put |
|---|---|---|
station | yes | A stop name, for example Marienplatz or Ostbahnhof |
limit | no | How many departures to return. The default is 10 |
transport_types | no | A list of transport types, for example SBAHN. The default covers UBAHN, SBAHN, TRAM, BUS, REGIONAL_BUS and BAHN |
To see only one type, pass that type alone in transport_types. Every other value is left at its default.
What comes back
The output has two fields: station and departures. Each departure has line, type, direction, platform, planned_ms, realtime_ms, delay_min, realtime, cancelled and notices.
Planned and live times come back as epoch milliseconds. Delay is given in minutes. Cancellations and station notices are included when MVG reports them.
In a live check on 7 November 2026 at 19:04, the Marienplatz stop returned 10 departures in 513 ms. The list included live delays, such as an S1 running 6 minutes late. The S-Bahn-only filter was checked at Ostbahnhof.
What leaves your computer
The recipe sends two requests, both to www.mvg.de. They leave from your own browser tab, with no login. These are the same two requests the MVG website makes for its departure monitor. Nothing goes through wield.run, and Wield does not send your results to any server of its own.
Limits and terms
The recipe is read-only. It cannot change or book anything. Each run is one lookup that you start yourself. Don't loop it to watch a stop for changes.
Wield caps every run at 12 steps, 40 requests and 60 seconds. This recipe uses two requests, well below those limits.
For the full set of MVG tools, see the MVG MCP server page. To plan a route rather than read a stop, use the MVG trip planner recipe.
FAQ
Do I need an MVG account?
No. The recipe needs no login. It reads the public departure data that the MVG website shows to anyone.
Can this recipe plan a trip between two stops?
No. Route planning is a separate recipe. See plan a trip with MVG.
Which transport types are included by default?
The default covers the U-Bahn, S-Bahn, tram, bus, regional bus and rail. Pass a shorter list in transport_types to narrow the results.
Which AI apps work with Wield?
Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. See AI apps that work with Wield for the full list.