{
  "markdown": "# mcp-tfl\n\nTransport for London (TfL) Unified API MCP — keyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `line_status` | Current service status for London transport lines. Pass either a comma-separated list of modes (e.g. \"tube,dlr\") OR a specific lineId (e.g. \"victoria\", \"central\"). Returns each line with lineStatuses + statusSeverityDescription (e.g. \"Good Service\", \"Minor Delays\"). |\n| `stop_search` | Search for stops/stations by name. Returns matches with a naptanId (the \"id\" field) used by the arrivals tool, plus modes, zone, and lat/lon. |\n| `arrivals` | Real-time predicted arrivals at a stop. Pass the naptanId from stop_search (e.g. \"940GZZLUOXC\"). Results are sorted by timeToStation (seconds away), nearest first. |\n| `plan_journey` | Plan a journey across London transport. from/to may be stop names, postcodes, or \"lat,lon\" coordinates. Returns journey options (legs, durations, modes). If a location is ambiguous, the API returns disambiguation options instead of journeys — refine the input or use a naptanId/coords. |\n| `bike_points` | London Santander Cycle hire scheme — live pushbike and empty-dock counts at each London cycle-hire docking point (bikes available, spaces free, total capacity in additionalProperties). London public bicycle rental only. Pass an optional area filter, e.g. \"Clerkenwell\"; omit for all London cycle docks. |\n| `disruptions` | Current disruptions for the given transport modes, with description and affected lines. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"tfl\": {\n      \"url\": \"https://gateway.pipeworx.io/tfl/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/tfl/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Tfl data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3610,
  "sha": "51f5d75de79a156a602bb0db5a37582117dee66303b4a74507109b10c02b498c",
  "repo_slug": "pipeworx-io/mcp-tfl",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_tfl_16f6de28/readme"
}