Skip to content
Official MCP RegistryListed

Transit MCP

Part ofTransit MCPlisted on 3 directories

Trips, departures, alerts and vehicles for NYC, DC and the SF Bay Area.

First seen 17 Oct 2026. Evidence as of 16 Nov 2026.

18
Tools
From an anonymous probe
1
Source listings
Each with its own history
50
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
find_transitCall with no arguments (or only `coverage`) to list the regions served and what each supports. Without a coverage, a name is searched in every region. If nothing matches, suggestions lists the closest names (not matches). Resolve a coverage, agency, route, station, stop, or a currently observed train number (where vehicle data exists); inspect an exact reference or nearby coordinates. Context ranks candidates without selecting identity. Candidates come best first (exact names and well-known place names such as SFO, then stations, then rail before bus), and each stop says what it is: stopType (station, platform or street stop), modes and the lines serving it, so you can pick the one the rider means. No general address geocoding. Use plan_trip for journeys.Read-only
get_all_stationsGet the complete list of transit stations with coordinates for one city. Large result; prefer search_stations or get_stations_by_line when looking for specific stations.Read-only
get_bus_positionsGet real-time positions of DC Metro buses, optionally filtered by route.Read-only
get_bus_predictionsGet real-time bus arrival predictions for a DC Metro bus stop.Read-only
get_bus_routesGet all DC Metro bus routes with route IDs and descriptions.Read-only
get_bus_stopsGet DC Metro bus stops. Returns all stops or filters by lat/lon/radius.Read-only
get_departuresFind what leaves a stop next, the first service or last service in a bounded window. Pass a stopRef from find_transit, or a stop name with its coverage: a name for one place covers all its stations in that network (otherStations lists the same place in other networks, such as the LIRR at Penn Station); a name for different places returns a question to ask, with candidates. A station covers its whole complex, e.g. every line at Times Sq-42 St; a platform ref covers that platform. Pass toStop or toStopRef for the next trips from here that stop at a destination, each with its arrival time there. Returns dated trip references for get_vehicle_status. For a journey with a change use plan_trip (with routes where needed): departures alone cannot prove a connection.Read-only
get_elevator_incidentsGet current elevator and escalator outages. DC Metro only.Read-only
get_incidentsGet current transit incidents and service advisories for DC Metro or NYC Subway.Read-only
get_route_infoGet detailed information about a transit route including service patterns. NYC Subway only.Read-only
get_service_statusCheck disruptions, delays, closures, elevator and escalator outages, or revalidate a chosen itinerary without replacing it. Scope by coverage, a station name with its coverage (stop), or an agency, route, stop or dated trip reference; a station covers its complex. Aggregate scopes include canonical service in the next 24 hours. equipment lists elevator/escalator outages: accessiblePath marks the step-free route, blocksStepFree marks stations step-free plan_trip avoids, and alternativeRoute is the agency's way around. Use get_vehicle_status for an observed vehicle location.Read-only
get_station_predictionsGet real-time train arrival predictions for a transit station. Supports DC Metro and NYC Subway. Accepts a station name or an exact station ID; if a name matches several stations, the result lists the candidates to choose from.Read-only
get_station_transfersGet transfer connections and nearby stations from a transit station. NYC Subway only.Read-only
get_stations_by_lineGet all stations on a specific transit line. Supports DC Metro and NYC Subway.Read-only
get_train_positionsGet real-time positions of all trains on the DC Metro system.Read-only
get_vehicle_statusWhere observed trains are right now. Pass a route ref to list its trains, a dated trip ref (from get_departures or a plan_trip leg) to find that train, or a station (stopRef, or a name with coverage) to see trains stopped at or heading to it; a station covers its whole complex. Each train reports the stop it is at or heading to (stopStatus), the stop it last served, and its destination. Coordinates are the vehicle's own when the agency sends them (DC); otherwise a stopped train is placed at its station and a moving one has none. Never pass a bare train number: use find_transit.Read-only
plan_tripPlan an origin-to-destination journey. Returns up to three independently validated itineraries (the fastest, then other lines); departure defaults to now. Pass the rider's place names as given: a name for one place (Penn Station, SFO) plans from or to all its stations. A name meaning different places (Broadway) returns the best trip from each, each labelled in reading and explained in notice: use the one the conversation points to, or ask the rider. The search covers every line of the coverage, buses included. When no itinerary is possible (planning unavailable, a search too large, or nothing found) it returns routeHints: lines near each end and direct lines serving both. Call again with routes (the lines you would ride, from routeHints or your own knowledge) to plan along only those lines, which works wherever schedules exist. Present only returned itineraries as confirmed. The whole journey must finish within windowSeconds (default two hours): if none is found for a long trip, retry with a larger window. Each transit leg carries a tripInstanceRef; pass it to get_vehicle_status to see where that train is now. For a wheelchair user or anyone avoiding stairs, set accessibility: "step_free": journeys then board, alight and change only at platforms step-free from the street per the agency (partial stations by direction), avoiding stations cut off by a current elevator outage; in-station changes between such platforms are taken as step-free. It refuses with ACCESSIBILITY_UNAVAILABLE when no current elevator report exists and ENDPOINT_NOT_STEP_FREE when an endpoint has no step-free platform now (get_service_status lists the outages). Never present a journey pieced together from get_departures as confirmed; check it here with routes.Read-only
search_stationsSearch for transit stations by name or code. Supports DC Metro and NYC Subway.Read-only

Change history

  1. plan_trip: input schema changed
  2. get_service_status: input schema changed
  3. server instructions changed (+"Live" +"for the SF Bay Area (BART, Muni, Caltrain, every 511 operator), Washington DC (Metrorail, Metrobus)" +"New York (subway, LIRR, Metro-North, buses).")
  4. Repository changed from "https://github.com/Aarekaz/metro-mcp" to "https://github.com/Aarekaz/transit-mcp" (registry)
  5. Description changed (registry)
  6. plan_trip: input schema changed
  7. plan_trip: description changed (+"lines);" +"Pass the rider's place names as given: a name for one place (Penn Station, SFO) plans from or to all its stations. A name meaning different places (Broadway) returns the best trip from each, each labelled in reading and explained in notice: use the one the conversation points to, or ask the rider." -"lines) and resolves named endpoints together;")
  8. get_service_status: input schema changed (+coverage, +itinerary, +ref, +stop)
  9. get_departures: input schema changed
  10. get_departures: description changed (+"coverage: a name for one place covers all its stations in that network (otherStations lists the same place in other networks, such as the LIRR at Penn Station); a name for" +"places returns a question to ask, with candidates." -"coverage (one station complex resolves directly;")
  11. find_transit: input schema changed (+context, +coverage, +latitude, +limit, +longitude, +query, +ref)
  12. server instructions changed (+"Public" +"trips, departures, alerts and live vehicles; find_transit lists the regions available now. Pass the rider's own place names; no lookup first. A to B: plan_trip. Next train or bus: get_departures (toStop: only trips reaching a destination). Delays, closures, elevators: get_service_status. Where a train is: get_vehicle_status. When a name means different places the result says so: choose by the conversation or ask the rider in place names. Say whether times are realtime or scheduled_only. Keep a rider posted: before they leave for a planned trip, recheck it with get_service_status, passing the itinerary exactly as plan_trip returned it (journeyValid, legChecks); if it no longer holds, plan again. For "is my train on time" call get_vehicle_status" +"the ride's tripInstanceRef, or get_departures at its boarding stop.")
  13. plan_trip: input schema changed
  14. get_vehicle_status: input schema changed
  15. get_service_status: input schema changed
  16. get_departures: input schema changed
  17. find_transit: input schema changed
  18. find_transit: description changed (+"If nothing matches, suggestions lists the closest names (not matches).")
  19. server instructions changed (+"Riders use everyday names ("Chinatown", "the Times Square station"). If a name finds nothing, use your own knowledge to retry with the official station name or a nearby landmark, or pass coordinates; suggestions (and a not-found error's candidates) are the closest names, not matches, so confirm one before relying on it.")
  20. plan_trip: description changed (+"(the fastest, then other lines)" +"The search covers every line of the coverage, buses included." +"unavailable,")
  21. get_service_status: input schema changed
  22. get_service_status: description changed (+"coverage, a station name with its" +"(stop),")
  23. get_bus_predictions: input schema changed
  24. find_transit: input schema changed
  25. find_transit: description changed (+"Call with no arguments (or only `coverage`) to list the regions served and what each supports. Without a coverage, a name is searched in every region.")
  26. plan_trip: input schema changed (+routes)
  27. plan_trip: description changed (+"journey." +"When no itinerary is possible (planning withheld, as in SF Bay; a search too large; or nothing found, such as a bus trip) it returns routeHints: lines near each end and direct lines serving both. Call again with routes (the lines you would ride, from routeHints or your own knowledge) to plan along only those lines, which works wherever schedules exist. Present only returned itineraries as confirmed." +"For a wheelchair user")
  28. get_vehicle_status: input schema changed
  29. get_service_status: input schema changed
  30. get_service_status: description changed (+"elevator and escalator outages," +"reference; a station covers its complex." +"equipment lists elevator/escalator outages: accessiblePath marks the step-free route, blocksStepFree marks stations step-free plan_trip avoids, and alternativeRoute is the agency's way around.")
  31. get_departures: input schema changed (+toStop, +toStopRef)
  32. get_departures: description changed (+"Pass toStop or toStopRef for the next trips from here that stop at a destination, each with its arrival time there." +"For a journey with a change use" +"(with routes where needed):")
  33. find_transit: input schema changed
  34. find_transit: description changed (+"Candidates come best first (exact names and well-known place names such as SFO, then stations, then rail before bus), and each stop says what it is: stopType (station, platform or street stop), modes and the lines serving it, so you can pick the one the rider means.")
  35. server instructions changed (+"To get from A to B call plan_trip. If it returns no itinerary it returns routeHints (lines near each end, and direct lines serving both): choose the lines you would ride, using your own knowledge of the network too, and call" +"again with routes. That plans along" +"those lines, and works where open search")
  36. search_sfbay_stations: tool removed
  37. plan_trip: tool added
  38. get_vehicle_status: tool added
  39. get_vehicle_positions: tool removed
  40. get_sfbay_station_predictions: tool removed
  41. get_sfbay_routes: tool removed
  42. get_sfbay_incidents: tool removed
  43. get_service_status: tool added
  44. get_departures: tool added
  45. find_transit: tool added
  46. server instructions changed (+"Resolve ambiguous" +"entities with find_transit; context may rank candidates but never silently establishes identity. Coverage availability is runtime data. Use find_transit to inspect coverage first. Call plan_trip only when coverage is available and its planning capability is true. Never construct, extend or repair an itinerary from departures or station predictions. Use get_service_status" +"disruptions or rechecking a chosen journey,")
  47. search_sfbay_stations: tool added
  48. get_vehicle_positions: tool added
  49. get_sfbay_station_predictions: tool added
  50. get_sfbay_routes: tool added
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registrycom.transitmcp/transit-mcp17 Oct 202616 Nov 20262