MVG (Munich public transport) MCP server: let your AI agent read live departures and plan trips in Munich
Wield is an MCP server that gives your AI agent two MVG tools: live departures at a stop, and trip planning between two stops in Munich. Both run in your own browser through the Wield extension and need no login. Each run makes two or three small requests, the same kind the MVG website makes. We checked both recipes live on 7 November 2026.
MVG (Munich public transport) Show live departures at a Munich public transport stop
Read-only, no loginPasses the daily check
Parameters (3)
What your agent gets
| Recipe | What it does | Login | Status (7 Nov 2026) |
|---|---|---|---|
mvg.de/get-departures | Next departures at a stop: line, type, direction, platform, planned and live time, delay in minutes, cancellations and notices | No | OK, live check |
mvg.de/search-connections | Trips between two stops on U-Bahn, S-Bahn, tram, bus and other transport types: departure, arrival, duration, changes and each leg | No | OK, live check |
get-departures takes a station name, a result limit (default 10) and an optional list of transport types. search-connections takes a from stop, a to stop and a datetime. The datetime needs a UTC offset, such as +01:00. Set arrive_by to plan by arrival time instead of departure. The how-to pages cover example prompts for both.
In our live check, Marienplatz returned 10 departures in 513 milliseconds, with live delays such as the S1 at +6 minutes. A trip from Marienplatz to Garching Forschungszentrum on a Monday at 09:00 returned five connections in 1.2 seconds. The first took 25 minutes with no changes on the U6.
How a request flows
- You ask your agent: "When does the next U-Bahn leave Marienplatz, and how do I reach Garching Forschungszentrum by 9:00?"
- The agent calls
find_recipe, thenrunwithmvg.de/get-departuresormvg.de/search-connections. - wield-mcp passes the run through a local bridge to the Wield extension.
- The extension sends the requests from an mvg.de tab, so they carry your browser session.
- The results go back to your agent. Nothing passes through wield.run.
What leaves your computer
Requests go only to www.mvg.de. A departure lookup makes two requests. A trip search makes three: two stop lookups and one routing call. Passwords and cookies never leave your computer. Wield logs each request on your computer, with the method, host, path, status and timing, and never logs bodies or query values.
MVG terms, in plain words
We have not completed a review of MVG's terms for these recipes, so read them before automated use. Each run makes only the small requests the MVG website makes, and each one starts when you ask your agent for it. Neither recipe needs your login, so Wield never uses your account here.
Limits and what is not working yet
- No benchmark yet. We have not compared these recipes with a browser agent, so this page makes no speed claim.
- Routing needs an offset. The routing call needs an offset in the datetime, such as
+01:00. Without it, the trip search does not work. - Scope. The recipes cover the Munich network the MVG planner covers, the MVV area.
- Departures show live data where available. Each departure has a
realtimeflag. Use the planned time when the live time is missing.
FAQ
Is there an official MVG MCP server?
Not that we know of as of 7 November 2026. Wield provides these two reads as recipes that run in your browser.
Which AI apps work with it?
Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. The AI apps page lists each one.
Does it need a login?
No. Both recipes run without an account.
How fresh are the departures?
Each departure carries the planned time and the live time, both in epoch milliseconds, plus the delay in minutes. It also says whether the departure is cancelled and lists any notices. In our check on 7 November 2026, Marienplatz returned live delays with its 10 departures.
How fast is it compared with a browser agent?
No comparison exists yet. These two recipes have no benchmark row. The benchmark hub lists the sites we have measured so far.