accident_statsLABSCO 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, with duration and step-by-step legs
- 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 — bunx @daanrongen/tfl-mcp
USE CASES
01
Planning a journey across modes
The full journey planner is here alongside line status and stop arrivals, so a route and the disruptions on it come back together.
02
Getting home when the line is down
Search for licensed taxi and minicab offices near where you are actually standing.
03
Checking the air before going outside
Live pollution forecasts covering NO2, O3, PM10, PM2.5 and SO2.
04
Making a case about a dangerous junction
Road accident statistics by year, from TfL's own record rather than a news report.
42 tools
Listed in project code.
air_qualitybike_point_searchbike_point_by_idcabwise_searchjourney_planline_searchline_lookupline_statusline_disruptionsline_routesline_route_sequenceline_stop_pointsline_arrivalsline_timetablemode_arrivalsoccupancy_car_parksoccupancy_bike_pointsoccupancy_charge_connectorsplace_searchplace_by_idplace_by_geoplace_by_typeroad_lookuproad_disruptionssearchstoppoint_searchstoppoint_by_idsstoppoint_lookupstoppoint_by_smsstoppoint_by_geostoppoint_service_typesstoppoint_arrivalsstoppoint_disruptionsstoppoint_reachable_fromstoppoint_directionstoppoint_routestoppoint_crowdingstoppoint_placesvehicle_emission_surchargevehicle_ulez_compliancevehicle_arrivalsBEFORE YOU INSTALL
What to know first
Tools you get
42 tools registered in the project's code.
Requires
bunx on PATH
Optional
TFL_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
bunx @daanrongen/tfl-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"tfl": {
"type": "stdio",
"command": "bunx",
"args": [
"@daanrongen/tfl-mcp"
],
"env": {
"TFL_API_KEY": "<YOUR_TFL_API_KEY>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --env TFL_API_KEY=<YOUR_TFL_API_KEY> --transport stdio tfl -- bunx @daanrongen/tfl-mcp
