Let Claude plan a trip on Munich public transport (MVG)
Wield lets Claude plan a trip on Munich public transport. Claude runs the mvg.de/search-connections recipe with a start stop, a destination and a time. The request runs in your own browser through the Wield extension. The result lists connections with departure and arrival times, duration, changes and each leg. Nothing passes through wield.run.
MVG (Munich public transport) Plan a trip on Munich public transport (U-Bahn, S-Bahn, tram, bus)
Read-only, no loginPasses the daily check
Parameters (5)
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.
No MVG account is needed. This recipe needs no login.
Ask your agent
Ask with the two stops and the time. For example:
"Plan a trip from Marienplatz to Garching Forschungszentrum on Monday at 09:00."
Claude calls find_recipe, then run with mvg.de/search-connections. It looks up both stops, then asks MVG's journey planner for routes at the time you gave.
Params: what to put where
| Param | Required | What to put |
|---|---|---|
from | yes | The start stop, for example Marienplatz, Hauptbahnhof or Garching |
to | yes | The destination stop |
datetime | yes | The date and time with a UTC offset, for example 2026-11-09T09:00:00+01:00 |
arrive_by | no | true makes datetime the latest arrival instead of the earliest departure. The default is false |
transport_types | no | A list of transport types. The default covers U-Bahn, S-Bahn, tram, bus, regional bus, rail, ferries and on-demand taxis |
Munich is on +01:00 in winter and +02:00 in summer. The offset is required. Without it, MVG's routing call returns HTTP 400, and the search fails.
What comes back
The output has three fields: from, to and connections. Each connection has departure, arrival, duration_min, changes and legs. Each leg names its line, direction, platform and stops.
Times come back as local ISO timestamps with the offset. Durations are calculated from those times.
In a live check on 7 November 2026 at 19:04, a Monday 09:00 search from Marienplatz to Garching Forschungszentrum returned 5 connections in 1.2 s. One of them was a U6 trip of 25 minutes with no changes. The check passed 5 of 5 tests.
What leaves your computer
The recipe sends three requests to www.mvg.de. Two look up the start and destination stops. One asks for routes. All three leave from your own browser tab. Nothing goes through wield.run.
The requests match the ones the MVG website makes for its journey planner.
Limits and terms
The recipe is read-only. It searches routes and does not book tickets or change anything. Each run is one search that you start yourself. Don't loop it to scan many times of day.
Wield caps every run at 12 steps, 40 requests and 60 seconds. Three requests stay well below those limits.
For live departures at one stop, use the departures recipe. The full set of MVG tools is on the MVG MCP server page.
FAQ
Does the result include ticket prices?
No. The output contains times, durations, changes and legs. It has no fare fields, so check fares in the MVG app or on the MVG website.
How do I search for a fixed arrival time?
Set arrive_by to true. Then datetime is the latest time you want to arrive, and the recipe returns routes that reach the destination by then.
Why did my search fail with HTTP 400?
The most common cause is a datetime without a UTC offset. Add the offset, for example +01:00 in winter, and run the search again.
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.