Skip to main content
Glama
Sign In
transport-gzm

transport-gzm

by Wiktor102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to transport-gzm

No user-submitted related servers found.

    Related Servers

    • rozklad-mcp

      ContentWriterco
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search Polish public transport timetables — trains, PKS/regional buses, and optionally urban transit in ~20 cities — by planning journeys with transfers, checking departures with platforms, and tracking live delays, cancellations and full trip details, all from open GTFS data without an API key. Station lookup tolerates typos and missing Polish diacritics, and endpoints can be a stop, a whole city, or coordinates.
      6
      117 npm
      34
      MIT

    • Moscow Transport MCP

      zavorateam
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access real-time public transport data for Moscow and the Moscow region, aggregating and reconciling information from multiple sources. Provides tools for finding stops, live arrival boards, vehicle tracking, route details, and ETA calculations.
      MIT

    • Live Transit MCP Server

      loama
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to query live public transport status, alerts, line maps and vehicle positions across worldwide networks through tools such as search, network_status, line_status, disruptions, airport and vehicles_near.
      MIT
    • transcapi-mcp

      transcapi-mcpofficial

      tcdataconsultants
      A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to live public transport data across Great Britain, enabling searches for stops and stations, real-time bus and rail departures, live vehicle positions, service disruptions, and door-to-door journey planning. All tools are read-only and require an API key.
      10
      29 PyPI
      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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct purpose: alerts vs alert_by_id, vehicles vs vehicle_by_id, next_arrivals for stop-specific predictions, trip_updates for delay info, feed_summary for metadata, and health for system status. No two tools overlap in functionality.

    Naming Consistency4/5

    Tools follow a clear pattern: plural names for list operations (alerts, vehicles, trip_updates) and 'by_id' for single items (alert_by_id, vehicle_by_id). feed_summary and health are unique but descriptive. next_arrivals deviates slightly but remains intuitive.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a transit data API. It covers all necessary operations without redundancy or bloat, making it efficient for agents to navigate.

    Completeness4/5

    The tool set covers core real-time transit data: vehicle positions, alerts, trip updates, stop arrivals, and system health. Missing static data like route or stop listings, but for live monitoring, it is sufficiently complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources