Onebusaway Mcp Server
Let your coding agent pull live bus stops, routes, arrivals, and vehicle positions from OneBusAway while you ship transit or mobility features.
Overview
io.github.cyanheads/onebusaway-mcp-server is a MCP server for the Build phase that exposes OneBusAway real-time transit stops, routes, arrivals, and vehicle positions to your agent.
What is this MCP server?
- Real-time stops, routes, schedules, arrivals, and vehicle positions via OneBusAway REST APIs
- STDIO (npm/Bun) and hosted streamable-http remote at onebusaway.caseyjhand.com/mcp
- Configurable ONEBUSAWAY_BASE_URL plus TEST API key for Puget Sound development
- Version 0.1.8 MCP server schema with Bun runtime hint for local stdio
- MCP_LOG_LEVEL for debuggable agent sessions during integration work
- Server version 0.1.8 per MCP server schema
- Default base URL https://api.pugetsound.onebusaway.org
- Supports stdio npm transport and hosted streamable-http remote endpoint
Community signal: 1 GitHub stars.
What problem does it solve?
Agents cannot reliably call OneBusAway unless you paste curl snippets or maintain custom tooling every time you need live arrival data.
Who is it for?
Indie devs building OneBusAway-backed trip planners, campus shuttles, or agent assistants in Puget Sound or other OBA deployments.
Skip if: Teams that need turn-by-turn routing, non-OneBusAway GTFS-only feeds without a compatible OBA API, or zero API setup.
What do I get? / Deliverables
After you register the server, your agent can query transit entities through MCP tools using your API key and base URL configuration.
- Registered MCP server exposing OneBusAway transit query tools
- Agent-callable access to stops, routes, schedules, arrivals, and vehicles
- Configurable instance targeting beyond default Puget Sound base URL
Recommended MCP Servers
Journey fit
Transit APIs belong on the Build shelf because solo builders wire them into apps, agents, and prototypes—not in abstract ideation alone. Integrations is the canonical subphase for MCP servers that expose a third-party HTTP API (OneBusAway) to Claude Code, Cursor, or Codex.
How it compares
MCP integration to OneBusAway transit APIs, not a standalone map UI skill or general web browser automation pack.
Common Questions / FAQ
Who is io.github.cyanheads/onebusaway-mcp-server for?
Solo builders and small teams shipping mobility or transit features who want Claude Code, Cursor, or Codex to read live OneBusAway data through MCP.
When should I use io.github.cyanheads/onebusaway-mcp-server?
Use it during Build when you integrate arrivals, stops, routes, or vehicle positions into an app, CLI, or agent workflow backed by OneBusAway.
How do I add io.github.cyanheads/onebusaway-mcp-server to my agent?
Install @cyanheads/onebusaway-mcp-server from npm, run start:stdio with Bun, set ONEBUSAWAY_API_KEY and optional ONEBUSAWAY_BASE_URL, or add the streamable-http remote URL in your MCP client config.