Onebusaway MCP Server

by cyanheads Your server? Claim it

answering

Onebusaway MCP Server is answering right now. Last checked 1 min ago. 436 installs a week from npm. It exposes 16 tools. Last commit 26 Oct 2026.

Real-time transit stops, routes, arrivals, vehicle positions, and schedules via OneBusAway APIs.

Installs per day peak 196 · avg 33 · +384% w/w

a month agotoday

Uptime history 91 days of history · worst day 0%

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

547 ms

Response time

average over 24h

436

Installs / week

npm and PyPI

What changed 33

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 August 2026. No other catalogue keeps this.

26 Oct 4 tool descriptions were rewritten onebusaway_get_block, onebusaway_get_schedule_for_route, onebusaway_get_schedule_for_stop and 1 more

26 Oct 3 tools changed the parameters they ask for onebusaway_get_block, onebusaway_get_schedule_for_route, onebusaway_get_schedule_for_stop

26 Oct a tool changed version

9 Oct a tool changed version

25 Sep 4 tools changed the parameters they ask for onebusaway_get_arrivals, onebusaway_get_schedule_for_route, onebusaway_get_schedule_for_stop and 1 more

25 Sep a tool description was rewritten onebusaway_get_block

25 Sep a tool appeared onebusaway_get_stop_context

25 Sep a tool changed version

19 Sep a tool changed version

24 Aug 15 tools changed the parameters they ask for onebusaway_find_routes, onebusaway_find_stops, onebusaway_get_alert and 12 more

and 1 more, back to 24 August 2026

Nothing serious here today

Today is the operative word: we check Onebusaway MCP Server every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add onebusaway-mcp-server --transport http https://onebusaway.caseyjhand.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://onebusaway.caseyjhand.com/mcp

~/.codex/config.toml

[mcp_servers.onebusaway-mcp-server]
url = "https://onebusaway.caseyjhand.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "onebusaway-mcp-server": {
      "url": "https://onebusaway.caseyjhand.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "onebusaway-mcp-server": {
      "type": "http",
      "url": "https://onebusaway.caseyjhand.com/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

onebusaway

onebusaway_find_routes

Find transit routes near a location, optionally filtered by name or number. Returns routes with IDs, short names, and descriptions. Use routeId values to fetch schedules, vehicles, or stop sequences.

onebusaway_find_stops

Find bus stops near a location. Returns stops within a radius, each with ID, name, direction, served routes, and wheelchair boarding status. Use stopId values from results to fetch real-time arrivals with onebusaway_get_arrivals. Optionally filter by stop code (the number printed on the stop sign, e.g. "75403").

onebusaway_get_alert

Fetch full detail for a service alert (situation) by ID. Returns the summary, description, reason (e.g. detour, construction), affected stops and routes, consequence description, and active time windows. Situation IDs appear in onebusaway_get_arrivals responses under situationIds and situations[].id.

onebusaway_get_arrivals

Real-time arrivals and departures at a stop. Returns predicted arrival times, schedule deviation (how many seconds late/early), vehicle positions, and any active service alerts. The predicted boolean on each arrival indicates whether GPS tracking backs the estimate — predicted=false means schedule-only. Use tripId from results for follow-up onebusaway_get_trip calls. Stop IDs use agency-prefixed format: {agencyId}_{localId} (e.g. "1_75403").

onebusaway_get_block

Fetch block trip sequences with their stop times and service-calendar conditions. Top-level fields describe the first returned configuration; every remaining alternative is included without choosing a calendar date. Optionally select an exact tripId or complete trips having any departure in a half-open GTFS-seconds interval, independently in every configuration; selection counts trip occurrences before and after filtering. Without selectors, returns all trips with no default cap. Block IDs appear as blockId in onebusaway_get_trip responses; obtain a tripId from onebusaway_get_arrivals first.

onebusaway_get_route

Fetch details for a specific route by ID. Returns short name, description, agency, route type, and schedule URL. Route IDs use agency-prefixed format: {agencyId}_{localId} (e.g. "1_100259").

onebusaway_get_schedule_for_route

Full-day schedule for a route — all trips, stop sequences, and departure times for the specified date (defaults to today). Optionally select an exact tripId or complete trips having any departure in a half-open GTFS-seconds interval; selection includes counts before and after filtering. Without selectors, returns all mapped trips with no default cap. For live predictions, use onebusaway_get_arrivals at specific stops instead.

onebusaway_get_schedule_for_stop

Full-day departure schedule for a stop. Lists every departure by route and direction for the specified date (defaults to today). Optionally filter departure rows by routeId and a half-open Unix-millisecond interval; selection includes counts before and after filtering. Without selectors, returns the complete mapped schedule with no default cap. For live predictions, use onebusaway_get_arrivals instead.

onebusaway_get_stop

Fetch details for a specific stop by ID. Returns the stop's name, coordinates, direction, served routes, and wheelchair accessibility. Stop IDs use agency-prefixed format: {agencyId}_{localId} (e.g. "1_75403" for Metro Transit stop 75403).

onebusaway_get_stop_context

Everything happening at a stop in one call: the stop's details, its real-time arrivals, and full detail for every service alert on the stop or on any arrival in the window. Returns what onebusaway_get_stop, onebusaway_get_arrivals, and one onebusaway_get_alert call per alert would, from a single upstream request — arrivals in the onebusaway_get_arrivals shape, alerts in the onebusaway_get_alert shape. The stop omits its served-route list; use onebusaway_get_stop for routeIds. Stop IDs use agency-prefixed format: {agencyId}_{localId} (e.g. "1_75403").

onebusaway_get_trip

Real-time status and stop sequence for a trip. Returns vehicle position, schedule deviation, current phase, and remaining stops. Use tripId from onebusaway_get_arrivals to look up a specific vehicle's progress.

onebusaway_get_vehicles

Real-time positions of active vehicles for an agency. Optionally filter to a single route (client-side). Returns GPS coordinates, counter-clockwise orientation from east, schedule deviation, and current trip. Reports agency records omitted for missing position coordinates. Use agencyId values from onebusaway_list_agencies.

onebusaway_list_agencies

List all transit agencies served by this OneBusAway instance. Returns agency IDs, names, contact info, timezone, and geographic coverage center. Agency IDs are needed for onebusaway_list_routes_for_agency and onebusaway_get_vehicles.

onebusaway_list_routes_for_agency

List all routes operated by an agency. Returns route IDs, short names, and descriptions. Use to enumerate an agency's full service before searching for a specific route. Get agencyId values from onebusaway_list_agencies.

onebusaway_search_routes

Search for routes by name or number. Returns matching routes with IDs. Use to resolve a route short name (e.g. "44") to a route ID for schedule or vehicle lookups with onebusaway_get_vehicles or onebusaway_get_schedule_for_route.

onebusaway_search_stops

Search for stops by name or code. Returns matching stops with IDs and coordinates. Use to resolve a human-readable stop name or number to a stop ID for arrivals lookups with onebusaway_get_arrivals.

Endpoints

URL	Transport	State	Latency	Checked
https://onebusaway.caseyjhand.com/mcp	streamable-http	answering	514 ms	1 min ago

Alternatives to Onebusaway MCP Server

same job, measured the same way

SF Muni Real-Time Transit

by srivastsh

Real-time SF Muni departures, routes, alerts, vehicle positions, and schedules.

11 tools answering

Septa MCP

by mrfentmen

SEPTA transit arrivals and vehicle positions.

60 installs/wk local only

Lviv Public Transport

by vbhjckfd

Lviv public transport MCP: stops, timetables, routes, and live vehicle positions. No API key.

9 tools answering

Carris Metropolitana

by thiagojacoblannes

Greater Lisbon buses: stops, real-time arrivals, lines, alerts and live vehicles.

352 installs/wk local only

Trimet

by pipeworx-io

TriMet MCP — live arrivals, stop lookup, vehicle positions and service alerts for Portland…

188 installs/wk 48 tools answering

Zoopit

by zoopit

Read-only access to a Zoopit account: orders, routes, fleet and live vehicle positions.

answering

Charlotte Area Transit (CATS)

by ajwann

Live CATS bus and light rail positions and arrival predictions from the agency's GTFS-Realtime feeds

1 installs/wk local only

Charlotte Area Transit (CATS)

by ajwann

CATS bus and light rail trip planning, live arrivals, timetables, routes, and service alerts

59 installs/wk answering

Onebusaway MCP Server — questions

Answers built from our own checks of this server.

What can Onebusaway MCP Server do?

It exposes 16 tools, read directly from the server on our last check. Among them: onebusaway_find_routes, onebusaway_find_stops, onebusaway_get_alert, onebusaway_get_arrivals, onebusaway_get_block, onebusaway_get_route and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Onebusaway MCP Server working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 547 ms. The bar chart above shows every period we have measured.

How do I connect Onebusaway MCP Server?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Onebusaway MCP Server need an API key?

No. Onebusaway MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Onebusaway MCP Server?

It answers our handshake in 547 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Onebusaway MCP Server?

The npm package @cyanheads/onebusaway-mcp-server was installed 436 times in the last week. Week over week that is +384%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Onebusaway MCP Server open source?

The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 2 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at onebusaway.caseyjhand.com, which runs on its operator's own terms.