Skip to main content
Glama

Related Servers

Alternatives to septa-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides real-time SEPTA transit data via the keyless SEPTA API, enabling users to query schedules, routes, and arrivals for Philadelphia's public transit system.
      11 npm
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude and other MCP clients to answer live questions about Toronto's transit network, including next arrivals, routes, connections, detours, accessibility and service advisories. It fetches TTC timetables and real-time feeds on demand, reporting data freshness and attaching relevant disruptions to each answer.
      19
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides real-time San Francisco Bay Area Rapid Transit data, enabling queries about BART schedules, routes, and station information through natural language.
      413 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language queries about live Belgian trains, metro, tram and bus services — departures, arrivals, A-to-B journey planning, disruptions and train composition — from Claude or any MCP client speaking Streamable HTTP. It runs remotely on Cloudflare Workers, needs no accounts, and stores no personal data.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to interact with Washington DC Metro (WMATA) transit system through natural language queries. Provides real-time train arrivals, service alerts, station information, trip planning, and accessibility updates.
      739 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role: station lookup, station departure board, origin-destination live trains, origin-destination schedules, train status, and alerts. The main possible overlap is between station_departures and next_trains, but the descriptions make the distinction reasonably clear: one station's board versus a specific origin-destination trip.

    Naming Consistency4/5

    All tool names use consistent snake_case and are readable. Most are noun-phrase style (station_departures, train_status) while find_station uses verb_noun, which is a minor deviation but not confusing.

    Tool Count5/5

    Six tools is well-scoped for a Regional Rail information server. Each tool covers a distinct transit query type without unnecessary bloat.

    Completeness5/5

    The surface covers the core Regional Rail workflows: station discovery, scheduled trips, live next trains, station departure boards, train status, and service alerts. No obvious operational gap remains for typical rider questions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues