Tfl MCP Server

MCP server for the Transport for London (TfL) Unified API — lines, journeys, stop points, arrivals, bike points, and more over stdio

Local serverstdio

What is the Tfl MCP MCP server?

MCP server for the Transport for London (TfL) Unified API — lines, journeys, stop points, arrivals, bike points, and more over stdio. That is what the tfl mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • Domain — Tools
  • AccidentStats — accident_stats
  • AirQuality — air_quality
  • BikePoint — bike_points_all, bike_point_search, bike_point_by_id
  • Cabwise — cabwise_search
  • Journey — journey_plan, journey_modes
  • Line — 14 tools
  • Mode — mode_active_service_types, mode_arrivals
  • Occupancy — 5 tools
  • Place — 7 tools
  • Road — 8 tools
  • Search — 5 tools

What it needs from you

Configuration is passed through the environment: TFL_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Tfl MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Tfl MCP's toolset — Domain, AccidentStats, AirQuality and 11 more — is a fair guide to whether it matches your workflow. It is maintained by daanrongen; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
DomainTools
AccidentStatsaccident_stats
AirQualityair_quality
BikePointbike_points_all, bike_point_search, bike_point_by_id
Cabwisecabwise_search
Journeyjourney_plan, journey_modes
Line14 tools
Modemode_active_service_types, mode_arrivals
Occupancy5 tools
Place7 tools
Road8 tools
Search5 tools
StopPoint17 tools
Vehicle3 tools

How to install the Tfl MCP MCP server

{
  "mcpServers": {
    "tfl": {
      "type": "stdio",
      "command": "bunx",
      "args": ["@daanrongen/tfl-mcp"],
      "env": {
        "TFL_API_KEY": "your-key-here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
TFL_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Tfl MCP to Domain.
  • Use Tfl MCP to AccidentStats.
  • Use Tfl MCP to AirQuality.

Frequently asked questions

It connects Tfl MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Domain, AccidentStats, AirQuality, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Tfl MCP directly.