Skip to main content
Glama

Related Servers

Alternatives to IDFM Transit MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to answer real-time questions about Paris public transport through the Île-de-France Mobilités PRIM API: searching stops, checking next departures, planning journeys, and listing traffic disruptions. Results come back as short, LLM-readable text, with API errors surfaced as clear tool errors rather than crashes.
      4
      MIT
    • 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
      8 npm
      4
      ISC
    • 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
      9 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target distinct intents (place search, journey planning, departures, stop info, journey checking). The only real overlap is get_line_status vs get_network_disruptions, both about disruptions, but descriptions differentiate per-line vs paginated network scope well enough. check_journey_status is clearly framed as validating a plan_journey result, distinguishing it from raw status tools.

    Naming Consistency5/5

    All seven tools follow a clean verb_noun snake_case pattern (search_places, plan_journey, get_line_status, get_stop_info, check_journey_status, etc.). No camelCase mixing or vague single-word verbs. Highly predictable.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and each maps to a distinct transit workflow (discovery, planning, status, departures, verification). No tool feels redundant or padded.

    Completeness4/5

    Covers the core transit lifecycle: place search, journey planning, realtime departures, line/network disruptions, stop details, and post-plan disruption checking. Minor gaps exist, such as fare/ticket info or explicit line schedule/stop-sequence retrieval, but agents can work around these via existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues