A
licenseA
qualityB
maintenanceAn 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.
3
8 npm
MIT
PTV Transit MCP Server
Related Servers
Alternatives to PTV Transit MCP Server
No user-submitted related servers found.
Related Servers
- 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.178 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
- AlicenseAqualityBmaintenanceEnables 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.10MIT
- AlicenseAqualityCmaintenanceEnables LLMs and developers to inspect, validate, and merge Transit Operational Data Standard feeds with GTFS supplements, query crew runs, vehicle block assignments, and deadheads, and run these operations via MCP or CLI.6MIT
- FlicenseNot gradedqualityBmaintenanceProvides VRR public transit data as MCP tools for Claude, enabling departure board lookups, trip planning with optional via stops, and disruption overviews.-
TDQS
A4.3/5.0
Scored across 4 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count4/5
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.
Completeness4/5
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.
Maintenance
ActivityStale
ResponsivenessNo issues