No sign in
Tools: 8
MCP App
Open Data

London Transit

Chat with AI and use the interactive dashboard.

Real-time London transport data — Tube line statuses, journey planning, live arrivals, bus routes, and Santander Cycles docking-station availability — powered by TfL Open Data.

Best forLondon CommutersTrip PlannersTransit DevelopersMultimodal Analysts

Try this workflow

Tube status now

What's the current status of every London Underground line right now? Highlight any lines with delays, suspensions, or part closures.

Use in your AI tool

Use the tools from this page

Opens ChatGPT on the web or desktop and asks it to use the WebMCP tools available here.

Connect the MCP server

You’ll sign in to MCPBundles when your client connects.

MCP URL
https://mcp.mcpbundles.com/bundle/london-transit

Chat in MCPBundles Studio

Sign in once, then chat here with saved access — one connection to many servers, with a history of what your AI ran.

Managed
Interactive app
8 tools
Agent guide included

Search with the interactive app or chat with AI — both work side by side.

Browse all tools
No sign in
Tools: 8
MCP App

Live probe refreshed Sep 14, 2026 · Endpoint host mcp.mcpbundles.com

What you can do with London Transit

Built for

London Commuters, Trip Planners, Transit Developers, Multimodal Analysts

Example workflows

Tube status now

The single most common London-resident question.

Try this

What's the current status of every London Underground line right now? Highlight any lines with delays, suspensions, or part closures.

Plan a journey

Demonstrates the journey planner with named stations.

Try this

Plan a journey from Westminster to King's Cross right now using public transport. Show duration, legs, and walking distance.

Bikes near Waterloo

Bike-share live availability — high-utility live data.

Try this

Which Santander Cycles docks within walking distance of Waterloo currently have at least 5 bikes available?

Context to know first

Where does the data come from?

Transport for London open data, covering Tube, DLR, Overground, Elizabeth line, buses, trams, river bus, and Santander Cycles. Data is real-time and proxied per request.

How accurate are live arrival predictions?

Predictions reflect TfL's best estimate at the moment of the request and can change without notice. Treat them as guidance, not a guarantee — especially during disruption.

Which modes are covered?

Every TfL-operated mode: Tube, DLR, Overground, Elizabeth line, buses, trams, cable car, river bus, and Santander Cycles bike share.

AI Skill
SKILL.md

Domain knowledge for London Transit — workflow patterns, data models, and gotchas for your AI agent.

London Transit (Transport for London Unified API)

Real-time data for London's entire public transport network. Powered by TfL Open Data.

Interactive Map App

An interactive map dashboard is available alongside this chat. When the app panel is open, your tool results are automatically forwarded to the map — do NOT call the app-open tool again. Just use the data tools below (get status, plan journey, search stops, etc.) and the map will update with the results rendered as map layers: tube lines as colored polylines, stations as markers, bike docks as colored circles, arrivals as floating boards.

Panel routing — start here

When the map panel is open, call the status, journey, or stop read that owns the data — do not call open app again.

User intentFirst panel readWhat the map shows
Cold-open the mapopen appEmpty map mount
Tube line disruptions / statustube status or line statusColored line polylines (line_status)
Plan A→B journeyjourney planJourney polyline (journey)
Find stops or stationssearch stopsStop markers (stop_search)
Santander Cycles docksbike pointsBike dock markers (bike_points)
Live board at a stopstop arrivals or line arrivalsArrivals overlay (arrivals)

Stop list clicks in the widget call stop arrivals with drill-down visibility — prefer that path when the user taps a stop in the panel.

Data Model

  • Lines — Transport lines across modes: tube, dlr, overground, elizabeth-line, bus, tram, cable-car, river-bus.
  • StopPoints — Stations, bus stops, piers. Identified by NaPTAN IDs (e.g. 940GZZLUVIC for Victoria Tube) or ICS codes (e.g. 1000248).
  • Predictions — Live arrival/departure predictions per line or stop. timeToStation is in seconds.
  • Journeys — Planned routes between two points with legs, duration, and fare information.
  • BikePoints — Santander Cycles docking stations with live bike/empty dock counts.

Key Patterns

  • Tube line IDs are lowercase: bakerloo, central, circle, district, hammersmith-city, jubilee, metropolitan, northern, piccadilly, victoria, waterloo-city, elizabeth.
  • Journey planner works best with ICS codes (the ics_id field from search results, e.g. 1000108 for Highbury & Islington). Also accepts NaPTAN IDs, Hub IDs (auto-resolved), or coordinates (lat,lon format as a string like 51.5074,-0.1278).
  • StopPoint search returns matches with both id (Hub/NaPTAN) and ics_id (ICS code) fields. Use ics_id for journey planning.
  • BikePoint additional properties contain NbBikes, NbEmptyDocks, NbDocks.
  • Line status severity: 10=Good Service, 9=Minor Delays, 6=Severe Delays, 5=Part Closure, 4=Planned Closure, 1=Part Suspended, 0=Suspended, 20=Service Closed.

Gotchas

  • Arrivals are unordered: The /Arrivals endpoint returns predictions in arbitrary order — sorted by timeToStation in tool output.
  • Journey planner station IDs: Use ICS codes (e.g. 1000266 for Westminster) or NaPTAN IDs (940GZZLUWSM). Full stop names don't work — use search stops first.
  • BikePoint full list is large: ~800 stations. Always search by area name.
  • Mode names: Use lowercase with hyphens: tube, dlr, overground, elizabeth-line, bus, tram, cable-car, river-bus.

Where the data comes from

Tool calls are proxied directly to the TfL Unified API with light normalization (sorted arrivals, resolved Hub/ICS/NaPTAN IDs, filtered modes). No caching, no transformation of source values.

Transport for London — Unified API
Transport for London (TfL)

Live operational data for London's public transport network: Tube/DLR/Overground/Elizabeth line statuses and arrivals, bus routes and live arrivals, journey planner, stop and station metadata, and Santander Cycles docking-station availability.

London-wide network — ~800 bike docks, ~20K stops, all TfL-operated lines
Source updated: Real-time
We refresh: Real-time (proxied per request, no caching)
JSON HTTP API
Greater London, UK
OpenStreetMap (basemap tiles)
OpenStreetMap contributors

Basemap tiles rendered by CARTO for the interactive map UI. Not used for any data lookup — display only.

Source updated: Continuous (community-edited)
We refresh: On client request (tiles served by carto CDN)
Raster PNG tiles
Global
Powered by TfL Open Data. Contains OS data © Crown copyright and database rights 2016, and Geomni UK Map data © and database rights 2019.
Live arrival predictions reflect TfL's best estimate at the time of the request and can change without notice. Do not use for safety-critical decisions.

Source availability last verified 2026-04-20.

Tools discovered (8)

  • London Transit Bike Points

    Search for Santander Cycles (bike-share) docking stations in London by name or area. Returns station names, locations, and IDs. Use a search term to find nearby docking stations rather than listing all ~800 stations. Do not call with an empty or generic query expecting a full catalogue — narrow the area name. Do not use this for live train or bus arrivals — those are stop-level or line-level live arrival boards. When the workspace panel is open, results update the panel automatically — do not ca

  • London Transit Journey Plan

    Plan a journey between two points on the London transport network. Returns route options with duration, legs, line changes, departure/arrival times, and step-by-step instructions. Use the stop-search tool first to find station ICS codes (use the 'ics_id' field from search results). Also accepts NaPTAN IDs, Hub IDs, or lat,lon coordinates. If TfL returns endpoint ambiguity (HTTP 300), resolve ICS or NaPTAN ids with stop search rather than retrying with free-text place names. Do not call stop-leve

  • London Transit Line Arrivals

    Get live arrival predictions for a specific TfL line, including London bus routes. Returns upcoming arrivals with station/stop names, platform, direction, destination, expected arrival times, and time to station in seconds. Use slug IDs for tube/rail ('victoria', 'central', 'dlr') or the route number for buses ('24', 'N29'). Optionally filter by direction or specific stop. Do not use this when the user named a hub or interchange without a line — call stop-level arrivals first. If you need arriva

  • London Transit Line Status

    Get the current service status of one or more specific TfL lines, including London bus routes. Returns status severity, description, and disruption reasons if any. Use slug IDs for tube/rail ('victoria', 'central', 'northern', 'dlr', 'elizabeth') or the route number for buses ('24', 'N29', '521'). Comma-separated for multiple lines/routes in a single call. Do not call this for a full-network mode overview — use the all-lines mode status overview instead. When you already have multiple ids, pass

  • London Transit Open App

    Open the London Transit interactive dashboard. Use this only when the user asks to open or view the TfL explorer before running a specific journey or status query. Use only when the user asks to open the panel before a specific data read. When the workspace panel is open, results update the panel automatically — do not call this tool again only to refresh the UI.

  • London Transit Search Stops

    Search for TfL stops and stations by name. Returns matching stops with their IDs (NaPTAN/ICS codes usable in journey planning), transport modes, zones, and coordinates. Filter results by transport mode. Do not paste a NaPTAN or ICS code as the query when you already know the stop id — use it directly for journey planning or stop-level live arrivals instead. When the user asked for one mode only, pass the modes filter so results stay on-network. When the workspace panel is open, results update th

  • London Transit Stop Arrivals

    Get live arrival predictions for a specific stop or station. Returns upcoming arrivals across all lines serving that stop, with platform, direction, destination, expected arrival time, and time to station in seconds. Use the stop-search tool first to find the station ID (Hub ID like 'HUBHHY', NaPTAN like '940GZZLUVIC', or ICS code). Do not call line-level arrivals when you need every line at one place — this tool is keyed by stop. After a 404 on the stop id, run stop search rather than guessing

  • London Transit Tube Status

    Get the current service status of all London Underground (Tube) lines, or any other TfL mode (DLR, Overground, Elizabeth line, bus, tram, etc.). Returns line names, status severity, descriptions, and any disruption details. Do not call this for one or two named routes or a single bus line — use line or route status lookup with the line / route id instead. Do not spam duplicate calls back-to-back for the same mode; status is not sub-second realtime. When the workspace panel is open, results updat

Frequently Asked Questions

Where does the data come from?

Transport for London open data, covering Tube, DLR, Overground, Elizabeth line, buses, trams, river bus, and Santander Cycles. Data is real-time and proxied per request.

How accurate are live arrival predictions?

Predictions reflect TfL's best estimate at the moment of the request and can change without notice. Treat them as guidance, not a guarantee — especially during disruption.

Which modes are covered?

Every TfL-operated mode: Tube, DLR, Overground, Elizabeth line, buses, trams, cable car, river bus, and Santander Cycles bike share.

How do I connect London Transit to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/london-transit. Authentication is handled automatically.

How many tools does London Transit provide?

London Transit provides 8 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.

What authentication does London Transit require?

London Transit uses open data APIs — no authentication required.

Setup Instructions

Connect London Transit to any MCP client in minutes

Try London Transit now

No API key or third-party login required. Open the interactive dashboard and start searching in seconds.