Skip to main content
Glama
Rumaisa10

TfL MCP Server

by Rumaisa10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to TfL MCP Server

No user-submitted related servers found.

    Related Servers

    • TfL Journey Status MCP Server

      anoopt
      A
      license
      C
      quality
      D
      maintenance
      Provides real-time access to Transport for London data, enabling users to check tube line statuses, get disruption details, and plan journeys between London locations. Uses the official TfL Unified API to deliver live transport information through AI assistants.
      3
      19 npm
      MIT

    • mcp-tfl-journey

      alisonborba
      A
      license
      B
      quality
      D
      maintenance
      Provides real-time Transport for London journey data, including routes, alerts, and disruptions, allowing AI assistants to search journeys and get station information.
      1
      9 npm
      4
      ISC

    • Tifa

      dazyoung
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query live London rail line status and the recorded history of disruptions, including filtered episodes, causes, period statistics and coverage gaps, through seven read-only tools.
      7
      MIT

    • traintracker

      hugorodgerbrown
      A
      license
      A
      quality
      B
      maintenance
      Lets Claude answer questions about GB National Rail trains, including live departures and arrivals, platforms, timetables, service details, and journey planning with live delay overlay.
      9
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (line status vs all-line status, bus arrivals vs train arrivals, nearby vs search vs station info). However, get_disruptions, get_planned_works, and get_line_status have some conceptual overlap around service conditions, and search_station vs get_station_info could be confused when resolving station identifiers.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun or verb_noun_qualifier pattern using snake_case, such as get_line_status, get_bus_arrivals, plan_journey, and search_station. There are no mixed conventions or vague standalone verbs.

    Tool Count5/5

    13 tools is well-scoped for a TfL transport server, covering lines, stations, arrivals, journeys, fares, buses, and disruptions without excessive sprawl. Each tool appears to earn its place.

    Completeness4/5

    The surface covers the core read-only TfL workflows: status, disruptions, planned works, station search/info, arrivals, journey planning, fares, and buses. Minor gaps exist, such as detailed line route/stop listings and potential ambiguity around how to obtain station IDs for arrivals, but agents can likely work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources