Toronto and GTA Transit
Server Details
Live TTC and Hamilton HSR transit: stop search, next departures, service alerts, vehicle positions.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool maps to a distinct object: departures at a stop, vehicles on a route, stop lookup, and system alerts, so there is little risk of picking the wrong one. However, the agency-resolution behavior differs across tools (next_departures errors on ambiguity, route_vehicles silently prefers TTC, search_stops returns an agency field), which makes tool behavior less predictable than the names suggest.
All four names are lowercase snake_case plural/collective resource nouns (next_departures, route_vehicles, search_stops, service_alerts) with a uniform, readable pattern. There is no mixing of camelCase, verb styles, or ad-hoc prefixes.
Four tools is a tight, focused surface that fits a single-domain transit server with no redundant entries. It sits slightly on the thin side, as there is no routing or proximity lookup, but every tool earns its place.
Core realtime reads (departures, vehicle positions, alerts) plus static stop search are covered, but there is no trip/journey planning, no nearby-stops-by-coordinate search, and no way to list or search routes, so some common transit queries dead-end. Agency support is also asymmetric, with HSR handling weaker than TTC in several tools.
Available Tools
4 toolsnext_departuresAInspect
Get the next departures for one stop on the TTC or Hamilton HSR. Static schedule candidates from the persistent schedule store are merged with GTFS Realtime trip updates (BusTime for the TTC, the City of Hamilton feed for HSR), and realtime entries replace matching scheduled entries. TTC and HSR stop ids can collide: pass agency to say which agency the stop belongs to. Without agency, a stop id that exists in both agencies returns an error naming both matches instead of guessing.
Inputs: stop_id (required), limit, agency.
route_vehiclesAInspect
Get live vehicle positions for one route from the agency GTFS Realtime vehicle positions feed. Pass agency to resolve the route inside one agency. Without agency the TTC is tried first and HSR second, so a route name that exists in both returns the TTC vehicles.
Inputs: route (required), limit, agency.
search_stopsAInspect
Find transit stops and stations by stop number, stop code, or name from the static GTFS feeds. Searches both the TTC and Hamilton HSR by default and merges the results; pass agency to search one agency only. Every result carries an agency field (TTC or HSR).
Inputs: query (required), limit, agency.
service_alertsAInspect
Get currently active service alerts. Defaults to the TTC, optionally filtered by mode to subway, bus, streetcar, or accessibility alerts; the mode filter applies to TTC alerts only. Pass agency hsr for Hamilton HSR alerts, or agency all for both agencies combined.
Inputs: mode, limit, agency.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Real-time SF Muni departures, routes, alerts, vehicle positions, and schedules.
Trips, departures, alerts and vehicles for NYC, DC and the SF Bay Area.
Get real-time NYC bus arrivals, live vehicle locations, and service alerts. Plan trips between any…
Plan San Francisco and Bay Area transit trips and check upcoming stop departures. Free, no API keys.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables Claude and other MCP clients to answer live questions about Toronto's transit network, including next arrivals, routes, connections, detours, accessibility and service advisories. It fetches TTC timetables and real-time feeds on demand, reporting data freshness and attaching relevant disruptions to each answer.19MIT
- AlicenseNot gradedqualityBmaintenanceProvides real-time NYC subway information including train arrivals, station search, service alerts, and nearby station finder using live MTA data with intelligent location handling.7MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server for Toronto Transit Commission (TTC) that exposes subway, streetcar, and bus schedules, real-time arrivals, vehicle positions, and service alerts, plus multi-modal trip planning.112 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables real-time Chicago Transit Authority train and bus tracking, including arrivals, positions, and predictions for CTA 'L' trains and buses.109 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.