Summary
Everything TfL publishes, in one server.
The API behind it is the one the TfL website runs on, generated here tool by tool — so when is the next one, is the line down, is there a dock free and can I drive there are all answerable in the same conversation.
What it is
An MCP server generated from the Transport for London Unified API, covering lines, journeys, stop points, bike points, occupancy, roads, places, vehicles, air quality and accident statistics. It runs locally over stdio.
What you get
- Full journey planning across all modes, plus the list of modes themselves
- Line status, routes, disruptions, arrivals, timetables and stop sequences
- Stop point search, arrivals, disruptions, crowding, routes, taxi ranks and car parks
- Santander Cycles availability across all docks, by search, or by dock id
- Occupancy for car parks, bike docks and EV charge connectors
- TLRN road status, disruptions, closures and roadworks
- ULEZ compliance, emissions surcharge and vehicle arrival tracking
- Live pollution forecasts for NO2, O3, PM10, PM2.5 and SO2, and road accidents by year
- Licensed taxi and minicab offices near a location
Requirements
Bunx on your PATH — launch is bunx against @daanrongen/tfl-mcp, over stdio. The data is Transport for London's Unified API, so the coverage is London.
Setup effort
One command plus a key — bunx @daanrongen/tfl-mcp, then supply credentials