MCP server for the Transport for London (TfL) Unified API — lines, journeys, stop points, arrivals, bike points, and more over stdio
MCP server for the Transport for London (TfL) Unified API — lines, journeys, stop points, arrivals, bike points, and more over stdio
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| 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 |
| StopPoint | 17 tools |
| Vehicle | 3 tools |
{
"mcpServers": {
"tfl": {
"type": "stdio",
"command": "bunx",
"args": [
"@daanrongen/tfl-mcp"
],
"env": {
"TFL_API_KEY": "YOUR_TFL_API_KEY"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| TFL_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
AI-native project management with persistent memory across IDEs (Claude, Cursor, Codex).
A model context protocol server to chat with iRacing data.
Structured failure knowledge for AI agents — dead ends, workarounds, error chains
MCP server for using the JFrog Artifactory API