PTV Transit MCP Server
Related Servers
Alternatives to PTV Transit MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLets MCP clients answer Adelaide Metro transit questions from the official GTFS timetable, including finding stops, listing routes at a stop, and checking scheduled departures and trip stop sequences. All tools are read-only, so users can plan direct trips and find where to get off without live delay data.5MIT
- AlicenseAqualityDmaintenanceAn MCP server exposing Greater Helsinki public transport data from Digitransit, enabling LLM hosts to answer live transit queries, plan journeys, and fetch stop departures via natural language.36 npmMIT
- AlicenseBqualityDmaintenanceMCP server that integrates with the transport12 API to provide tools for searching stops, routes, arrivals, and vehicle forecasts, enabling natural language interaction with public transport data.1711 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides tools to search stops, get next departures, and retrieve service alerts from Metlink's real-time public transport data, enabling natural language queries about Wellington transit.MIT
- AlicenseAqualityCmaintenanceEnables LLM clients to search stops, plan journeys, check live departures, service alerts, nearby locations, and vehicle positions using Transport for NSW open data, with per-request API key authentication.101MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
TDQS
Scored across 4 tools
Each tool has a distinct purpose: searching stops, listing routes, fetching departures, and running raw SQL queries. Despite get_next_departures taking a stop name, it clearly returns departures not stops, so there is no ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case: search_stops, list_routes, get_next_departures, run_sql_query. This is uniform and predictable.
Four tools is on the lower end of the typical range, but each covers a fundamental need for a transit information server. The count feels slightly thin yet not unreasonable for the scope.
Core operations are covered: stop search, route listing, and departures. Missing features like route-specific stop lists or trip planning are mitigated by run_sql_query, which allows direct access to the GTFS database. No critical dead ends.