プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。レビューとアカウント機能は今後のステップで始まります。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

Onebusaway MCP Server

作者:cyanheadsバージョン 0.3.0i★ –iパソコンでもクラウドでも
レジストリ名io.github.cyanheads/onebusaway-mcp-server

インストール

概要

作者による説明(英語の原文)

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

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: パソコンでもクラウドでも
  • トランスポート: stdio, Streamable HTTP
  • カテゴリ: 旅行・地図・天気

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

  • 基本チェック:3項目中3項目に合格
  • 作者のサーバーで動きます。あなたが頼んだ内容は、作者のサーバーを通ります。
  • できること:16件(ツール) onebusaway_list_agencies, onebusaway_find_stops, onebusaway_find_routes, onebusaway_search_stops …
  • 自分で入力するもの: ONEBUSAWAY_API_KEY, ONEBUSAWAY_BASE_URL, ONEBUSAWAY_RATE_LIMIT_REQUESTS, ONEBUSAWAY_RATE_LIMIT_WINDOW_MS, ONEBUSAWAY_RATE_LIMIT_MAX_WAIT_MS, MCP_LOG_LEVEL

必要なもの

  • クラウドで動くインストール不要。インターネット経由でつながります
  • npmNode.jsのインストール(npxコマンドに必要)

どのアプリを使っていますか?

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

ウェブ、デスクトップ、モバイルのClaudeで使えます:

  1. Settings → Connectors を開く
  2. Add custom connector を押す
  3. 下のアドレスを貼り付けて Add を押す
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Add2https://…3
https://onebusaway.caseyjhand.com/mcp

または、パソコンで動かす

Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます

{
  "mcpServers": {
    "onebusaway": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/onebusaway-mcp-server"
      ],
      "env": {
        "ONEBUSAWAY_API_KEY": "your-value",
        "ONEBUSAWAY_BASE_URL": "your-value",
        "ONEBUSAWAY_RATE_LIMIT_REQUESTS": "your-value",
        "ONEBUSAWAY_RATE_LIMIT_WINDOW_MS": "your-value",
        "ONEBUSAWAY_RATE_LIMIT_MAX_WAIT_MS": "your-value",
        "MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

ターミナルでこれを実行します

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

または、パソコンで動かす

claude mcp add onebusaway --env ONEBUSAWAY_API_KEY=your-value --env ONEBUSAWAY_BASE_URL=your-value --env ONEBUSAWAY_RATE_LIMIT_REQUESTS=your-value --env ONEBUSAWAY_RATE_LIMIT_WINDOW_MS=your-value --env ONEBUSAWAY_RATE_LIMIT_MAX_WAIT_MS=your-value --env MCP_LOG_LEVEL=your-value -- npx -y @cyanheads/onebusaway-mcp-server

動かす前に、空欄の値を入力してください。

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

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

または、パソコンで動かす

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

{
  "mcpServers": {
    "onebusaway": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/onebusaway-mcp-server"
      ],
      "env": {
        "ONEBUSAWAY_API_KEY": "your-value",
        "ONEBUSAWAY_BASE_URL": "your-value",
        "ONEBUSAWAY_RATE_LIMIT_REQUESTS": "your-value",
        "ONEBUSAWAY_RATE_LIMIT_WINDOW_MS": "your-value",
        "ONEBUSAWAY_RATE_LIMIT_MAX_WAIT_MS": "your-value",
        "MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

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

または、パソコンで動かす

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "servers": {
    "onebusaway": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/onebusaway-mcp-server"
      ],
      "env": {
        "ONEBUSAWAY_API_KEY": "your-value",
        "ONEBUSAWAY_BASE_URL": "your-value",
        "ONEBUSAWAY_RATE_LIMIT_REQUESTS": "your-value",
        "ONEBUSAWAY_RATE_LIMIT_WINDOW_MS": "your-value",
        "ONEBUSAWAY_RATE_LIMIT_MAX_WAIT_MS": "your-value",
        "MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

ChatGPTがつなげるのは、インターネット上のサーバーだけです:

  1. ウェブ版のChatGPTを開き → Settings → Connectors (Apps)
  2. Create または Add を押す(プランによっては、先に Advanced で Developer mode をオンにする必要があります)
  3. 下のアドレスを貼り付け、名前を付けて保存する
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Create2https://…3
https://onebusaway.caseyjhand.com/mcp

メニューの名前は、プランや時期によって少し違うことがあります。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

  • ONEBUSAWAY_API_KEY env
    OneBusAway API key. TEST works on the Puget Sound instance for development.
  • ONEBUSAWAY_BASE_URL env
    Base URL for the OneBusAway instance. Defaults to Puget Sound.
  • ONEBUSAWAY_RATE_LIMIT_REQUESTS env
    Upstream requests the pacer allows per window.
  • ONEBUSAWAY_RATE_LIMIT_WINDOW_MS env
    Width of the pacer's sliding rate window, in milliseconds.
  • ONEBUSAWAY_RATE_LIMIT_MAX_WAIT_MS env
    Longest a call may wait in the pacer queue, in milliseconds. Keep it under the SDK client's 60 s request timeout.
  • MCP_LOG_LEVEL env
    Sets the minimum log level for output (e.g., 'debug', 'info', 'warning').

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが2026年11月7日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

  • 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_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

  • 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_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.

  • 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_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_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_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_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=fa

  • 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 woul

  • 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

  • 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_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 d

  • 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 ag

  • 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 se

  • 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 fil

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月8日にチェック

  • ✓ 合格

    作者とリポジトリが一致

    レジストリ名は、リポジトリを所有するGitHubアカウント cyanheads で確認済みです

  • … 未チェック

    今もメンテナンスされている

    このリポジトリはまだGitHubから読み取っていません

  • … 未チェック

    ライセンスがある

    このリポジトリはまだGitHubから読み取っていません

  • ✓ 合格

    エンドポイントが応答する

    223ミリ秒で応答(HTTP 200)

  • – 対象外

    OAuthでサインイン

    サインイン不要

  • ✓ 合格

    ツールの説明に隠れた指示がない

    16件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

旅行・地図・天気のほかのサーバーとの比較i

  • このカテゴリのほかの1720件のうち0%よりスターが多い
  • このカテゴリのほかの1720件のうち69%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの1720件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Onebusaway MCP Serverは安全ですか?

当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか?

レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。

パソコンで動きますか、それともクラウドですか?

どちらでも使えます。パソコンにインストールしても、クラウド版につないでもかまいません。

今もメンテナンスされていますか?

GitHubリポジトリの最終更新は–、最新バージョン(0.3.0)がレジストリに届いたのは13 日前です。

どのアプリで使えますか?

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。

代わりに使えるものは?

同じカテゴリには:Galapagos Trip Planner, Simvito eSIM, Temporal MCP Server

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i

Galapagos Trip Planner

Galapagos trip cost, island-hopping plans, ferry times, weather, wildlife and park fees.

作者:galapagosislands.info初期今日更新

クラウドで動く✓ galapagosislands.info

Simvito eSIM

Compare travel eSIM plans and each local network (4G/5G), check phone support, get payment links.

作者:SimvitoTeam初期今日更新

クラウドで動く✓ simvito.com

Temporal MCP Server

Time, timezone and duration tools — IANA zones, conversion, DST-correct date arithmetic.

作者:jordanburke初期↓ 110/週今日更新

パソコンでもクラウドでも

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

@cyanheads/onebusaway-mcp-server Query stops, routes, real-time arrivals, vehicle positions, and schedules from OneBusAway transit APIs via MCP. STDIO or Streamable HTTP. 16 Tools • 2 Resources

Public Hosted Server: https://onebusaway.caseyjhand.com/mcp


Overview

Real-time transit from OneBusAway, set up for Puget Sound (King County Metro, Sound Transit, Pierce Transit, Community Transit, and more) and compatible with any OneBusAway instance. Find stops and routes, track live arrivals and vehicle positions, and pull schedules and service alerts.

Tools
ToolDescription
onebusaway_list_agenciesList the transit agencies on the instance, with IDs, contact info, and coverage area
onebusaway_find_stopsFind stops near a lat/lon, optionally filtered by stop code
onebusaway_search_stopsResolve a stop name or code to a stop ID
onebusaway_get_stopFetch one stop by ID
onebusaway_find_routesFind routes near a lat/lon, optionally filtered by name or number
onebusaway_search_routesResolve a route name or number to a route ID
onebusaway_get_routeFetch one route by ID
onebusaway_list_routes_for_agencyList every route an agency operates
onebusaway_get_arrivalsReal-time arrivals and departures at a stop, with schedule deviation, vehicle positions, and active alerts
onebusaway_get_stop_contextStop details, real-time arrivals, and full detail for every alert at the stop, from one upstream request
onebusaway_get_alertFull service alert detail by situation ID
onebusaway_get_tripReal-time status and stop sequence for a trip
onebusaway_get_blockEvery trip one vehicle runs in a service day, in order, with stop times
onebusaway_get_vehiclesReal-time positions of an agency's active vehicles, optionally for one route
onebusaway_get_schedule_for_stopFull-day departure schedule for a stop, by route and direction
onebusaway_get_schedule_for_routeFull-day schedule for a route: every trip and its stop sequence
Resources
ResourceDescription
onebusaway://stop/{stopId}Stop metadata: name, coordinates, served routes, wheelchair accessibility
onebusaway://route/{routeId}Route metadata: short name, description, agency, schedule URL

The same data is available to tool-only clients through onebusaway_get_stop and onebusaway_get_route.

Capability reference

onebusaway_list_agencies tool
  • No input; returns every agency with id, contact info, timezone, and coverageCenter / coverageSpan
  • limitExceeded flags an upstream-capped list, with no pagination to fetch the rest

onebusaway_find_stops tool
  • lat / lon required; radius in meters, default 300, max 1600; optional query matches the stop code printed on the sign
  • Each stop carries id, code, direction, routeIds, and wheelchairBoarding (ACCESSIBLE / NOT_ACCESSIBLE / UNKNOWN); limitExceeded means more stops exist within the radius

onebusaway_search_stops tool
  • query (stop name fragment or stop code) required; maxCount up to 100, default 10
  • Same stop shape as onebusaway_find_stops; limitExceeded means more stops matched than maxCount

onebusaway_get_stop tool
  • Single stopId; returns name, code, coordinates, direction, routeIds, and wheelchairBoarding
  • Unknown IDs fail as stop_not_found, with recovery via onebusaway_find_stops or onebusaway_search_stops

onebusaway_find_routes tool
  • lat / lon required; radius in meters, default 500, max 1600, or a latSpan + lonSpan box (both set) in its place; optional query by route name or number
  • Each route carries shortName, longName, agencyId, GTFS type (0=tram … 5=cable_car), color, and schedule url; limitExceeded means more routes exist in the area

onebusaway_search_routes tool
  • query (route name or number) required; maxCount up to 100, default 10
  • Returns shortName, longName, agencyId, and GTFS type; limitExceeded means more routes matched than maxCount
  • Fails as endpoint_unavailable on instances whose route-search endpoint returns 404, Puget Sound among them; use onebusaway_find_routes or onebusaway_list_routes_for_agency instead

onebusaway_get_route tool
  • Single routeId; returns shortName, longName, description, agency, GTFS type, color, and schedule url
  • Unknown IDs fail as route_not_found, with recovery via onebusaway_find_routes or onebusaway_search_routes

onebusaway_list_routes_for_agency tool
  • agencyId required; unknown agencies fail as agency_not_found
  • Every route with shortName, longName, GTFS type, color, and url; limitExceeded flags an upstream-capped list with no pagination

onebusaway_get_arrivals tool
  • stopId required; the window is minutesBefore (integer 0–60, default 5) / minutesAfter (integer 0–240, default 35), with longer horizons left to onebusaway_get_schedule_for_stop; unknown stops fail as stop_not_found
  • Each arrival carries predicted (false = schedule-only), scheduleDeviation in seconds (positive = late, meaningful only when predicted), predictedArrivalTime, vehiclePosition, stopsAway, and tripId
  • Active alerts arrive in situations[]: those on the stop itself plus those linked from each arrival's situationIds, each once

onebusaway_get_stop_context tool
  • Same input as onebusaway_get_arrivals, and the same stop_not_found / rate_limited failures; one call issues one upstream request
  • Returns stop (the onebusaway_get_stop fields minus routeIds), arrivals in the onebusaway_get_arrivals shape, and alerts in the onebusaway_get_alert shape — every alert on the stop or on an arrival in the window, including stop-wide alerts no arrival in the window carries
  • When the upstream response omits the stop, stop is null; a referenced alert missing from the response is left out; either way a notice names the tool to fetch it with

onebusaway_get_alert tool
  • Single situationId, from onebusaway_get_arrivals (situations[].id or arrivals[].situationIds); unknown IDs fail as situation_not_found
  • Returns a TPEG reason code, severity, consequenceMessage, affects (agency, route, stop, or trip scope), consequences with diversion stop IDs, and activeWindows

onebusaway_get_trip tool
  • tripId required; serviceDateMs (non-negative integer, midnight local) only for a trip on a previous service day; includeSchedule (default true) adds the stop sequence with GTFS times and distanceAlongTripMeters
  • status carries phase (e.g. in_progress, layover_before), predicted, position, scheduleDeviation, and nextStop; blockId (null when the trip has none) feeds onebusaway_get_block
  • Fails as trip_not_found when the trip isn't active for the service date; a completed trip's times come from onebusaway_get_schedule_for_route

onebusaway_get_block tool
  • Single blockId, from onebusaway_get_trip; unknown IDs fail as block_not_found
  • Top-level trips, activeServiceIds, and inactiveServiceIds describe the first returned configuration; alternateConfigurations preserves every remaining configuration in order. Service IDs are calendar conditions, not a claim that a configuration operates today
  • Each trip carries distanceAlongBlock, accumulatedSlackTime (layover seconds), and blockStopTimes. Optional exact tripId or departureFromSec / departureBeforeSec selects complete trips independently in every configuration, retaining empty configuration slots
  • With selectors, selection.total / returned count trip occurrences across configurations; configurationCounts[0] describes the top-level configuration, then one entry per alternative

Example: {"blockId":" ","departureFromSec":86400,"departureBeforeSec":90000} selects trips with any departure from 24:00 inclusive to 25:00 exclusive, retaining their complete stop sequences.


onebusaway_get_vehicles tool
  • agencyId required, unknown agencies fail as agency_not_found; optional routeId is filtered client-side after all of the agency's vehicles are fetched
  • Each vehicle carries position, orientation, phase, scheduleDeviation, tripId, nextStop, and predicted (reporting real-time GPS); limitExceeded flags an upstream-capped list with no pagination
  • tripId prefers the active trip; route and headsign metadata resolve only from that trip. orientation preserves counter-clockwise degrees from east (0=east, 90=north, 180=west, 270=south), not a compass bearing
  • Records missing latitude or longitude are skipped: omittedWithoutPosition counts them across the agency, and omittedWithoutPositionOnRoute counts resolved matches when filtering by route. These counts are independent of upstream truncation

onebusaway_get_schedule_for_stop tool
  • stopId required; optional date as a real YYYY-MM-DD calendar date, default (omitted or blank) today in the agency's timezone; unknown stops fail as stop_not_found
  • Departures grouped by route and direction, each with scheduledDepartureTime and tripId
  • serviceDateMs preserves the upstream schedule-date marker: query time for an omitted/blank date, instance-local midnight for an explicit date; it is not rounded to a service-day boundary
  • Optional routeId, `d

冒頭だけを表示しています。続きはリポジトリで読めます

PopNxに聞く