F
licenseNot graded
qualityB
maintenanceMCP server exposing live MBTA V3 transit data, with tools for routes, stops, arrivals, alerts, and vehicle positions.
-
RedTransporteMCP
by iiroak
Related Servers
Alternatives to RedTransporteMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Chelaile realtime public transit data in China, including bus and metro arrivals, vehicle positions, nearby stops, timetables, and route planning. It runs locally over stdio with no login or account configuration required.15250 npm19MIT
- AlicenseNot gradedqualityAmaintenanceEnables querying stops, routes, real-time arrivals, vehicle positions, and schedules from OneBusAway transit APIs via MCP, supporting STDIO or Streamable HTTP.73 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server for consulting official ANTT transport data in read-only mode via a hosted HTTP endpoint. Works with any MCP-compatible client, including Claude, ChatGPT, and Cursor.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for the Mobilerun platform, exposing tools for device control, workflow automation, task management, and platform operations via a stateless HTTP or stdio interface with bearer-token authentication and policy-based access control.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that provides tools for querying live transit data (stops, departures, routes, vehicles, alerts) from any WP GTFS Pro site, enabling AI assistants to answer rider questions.3 npmGPL 2.0
TDQS
A3.6/5.0
Scored across 15 tools
Disambiguation4/5
Tools are mostly distinct with clear purposes: stop lookup (search_stops/get_stop/find_nearby_stops), route lookup (list_routes/get_route/get_route_stops/get_route_shape), and journey planning (plan_journey/suggest_direct_routes). Some minor boundary overlap exists between route stop listing (get_route_stops, get_route) and spatial queries (find_nearby_stops, find_closest_station, get_routes_near_point, find_stops_in_bbox), which could cause some ambiguity but descriptions help disambiguate them.
Naming Consistency4/5
Names mostly follow a consistent get_/find_/list_/search_/suggest_/plan_ prefix pattern with descriptive object suffixes. Minor inconsistencies: mix of get_/find_/list_ for data retrieval operations is permissible but not perfectly uniform, and get_system_stats vs get_gtfs_status are somewhat similar in style. Overall predictable and readable.
Tool Count5/5
15 tools is on the higher end but appropriate for a comprehensive transit MCP server covering stops, routes, journey planning, arrival predictions, and dataset health. Each tool appears to earn its place covering distinct data needs.
Completeness4/5
The surface is comprehensive: spatial queries (nearby, bbox), route listing/detail/geometry, stop search/detail, arrivals, journey planning with mode and fare options, plus GTFS dataset status. Minor gaps exist, such as direct route-to-route stop exploration without coordinates (though get_route covers this), and no route filtering by arrival time, but the core transit workflows are well covered.
Maintenance
ActivitySlowing
ResponsivenessNo issues