cta_bus_predictions
Pack: cta · Endpoint: https://gateway.pipeworx.io/cta/mcp
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
| Name | Type | Required | Description |
|---|---|---|---|
stop_id | string | no | CTA bus stop id (stpid), the number on the bus-stop sign, e.g. “1926”. Comma-separable up to 10. |
route | string | no | Optional bus route number to filter, e.g. “22”, “66”, “X49”. Required when using find_stop. |
find_stop | string | no | Stop-name fragment to look up when stop_id is unknown, e.g. “clark & madison”, “michigan & randolph”. Requires route. |
direction | string | no | Optional direction to narrow find_stop, e.g. “Northbound”, “south” |
max | number | no | Max predictions to return, 1-20 (default 10) |
_apiKey | string | no |
Example call
curl -X POST https://gateway.pipeworx.io/cta/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"cta_bus_predictions","arguments":{}}}'Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"cta": {
"url": "https://gateway.pipeworx.io/cta/mcp"
}
}
}See Getting Started for client-specific install steps.