transit
Related Servers
Alternatives to transit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve live transit departures, vehicle positions, and service alerts for San Francisco Bay Area transit operators via the regional 511.org open-data API.86 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to answer Boston transit questions from live public data: upcoming MBTA departures and service alerts, nearest Bluebikes bikes and docks, nearby stops and stations, and door-to-door trip options across walking, biking, and transit. Every result reports its sources and as-of time, and the server is read-only.46 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceProvides real-time San Francisco Bay Area Rapid Transit data, enabling queries about BART schedules, routes, and station information through natural language.95 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to access real-time and scheduled public transit data, including routes, stops, departures, and service alerts, across multiple US metropolitan areas.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to find Bay Area places and stops and plan complete door-to-door journeys — walking legs, transit routes, transfers, and departure/arrival times, including deadlines and comparisons with walking or cycling — without API keys or authentication. Results come as readable itineraries plus structured data, with an interactive itinerary widget in supporting clients.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying real-time BART and SF Muni transit data, including departures, trip planning, fares, advisories, routes, alerts, vehicle positions, and schedules, from any MCP-compatible client.1MIT
TDQS
Scored across 6 tools
Each tool targets a distinct resource: operators, lines, stops, departures, vehicles, and alerts. Descriptions explicitly cross-reference when to use which (e.g., 'Don't use when' sections), eliminating ambiguity. No two tools overlap in purpose.
All tools share the 'transit_' prefix and follow a consistent verb-object pattern: list_operators, list_lines, find_stops, next_departures, list_vehicles, list_service_alerts. Minor variation between 'list', 'find', and 'next' but the style is uniform and predictable.
Six tools are well-scoped for a transit information server, covering discovery (operators, lines, stops), real-time queries (departures, vehicles), and alerts. No tool is redundant, and the count feels neither sparse nor bloated.
The tool surface covers the full workflow of querying transit info: discover agencies, lines, stops, then get live departures, vehicle positions, and alerts. A minor gap is the lack of a dedicated scheduled timetable tool, though the departures endpoint includes aimed times. Overall, the domain is well covered.