cta_bus_predictions
ActiveTool of Cta
declared in 0.1.0
Chicago CTA bus tracker arrival predictions at a bus stop — route, destination, predicted minutes until arrival ("DUE" = arriving now), delay flag, and vehicle id. Pass stop_id (the 4-5 digit stop number posted on CTA bus-stop signs), optionally with route. If you only know the stop by name, pass route + find_stop (a street/intersection fragment like "clark & madison") and the stop is looked up for you. Example: cta_bus_predictions({ route: "22", find_stop: "addison" })
Parameters schema
{
"type": "object",
"properties": {
"max": {
"type": "number",
"description": "Max predictions to return, 1-20 (default 10)"
},
"route": {
"type": "string",
"description": "Optional bus route number to filter, e.g. \"22\", \"66\", \"X49\". Required when using find_stop."
},
"_apiKey": {
"type": "string",
"description": "Optional: your own CTA credentials as \"train_key:bus_key\" — Train Tracker key (free at transitchicago.com/developers) + Bus Tracker key (free at ctabustracker.com)"
},
"stop_id": {
"type": "string",
"description": "CTA bus stop id (stpid), the number on the bus-stop sign, e.g. \"1926\". Comma-separable up to 10."
},
"direction": {
"type": "string",
"description": "Optional direction to narrow find_stop, e.g. \"Northbound\", \"south\""
},
"find_stop": {
"type": "string",
"description": "Stop-name fragment to look up when stop_id is unknown, e.g. \"clark & madison\", \"michigan & randolph\". Requires route."
}
}
}No endpoints wrapped at confidence ≥ 0.70.
Parent server
Cta
https://github.com/pipeworx-io/mcp-cta
1/7 registries