@pipeworx/odpt

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/odpt’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 4

Japan train timetables and live train information from ODPT (Public Transportation Open Data Center): station lookup in English or Japanese, scheduled station and train timetables, and live service status (normal / delayed / suspended) for Tokyo Metro, JR East, Toei and many other Japanese railway operators.

Tools

Auth

Every tool takes an optional _apiKey. Pipeworx supplies an ODPT developer consumer key for you (PLATFORM_ODPT_KEY, stored in the gateway’s encrypted platform-key store, not as an individual Worker secret — see docs/gateway-text-binding-limit.md), sent upstream as the acl:consumerKey query parameter (that is literally the parameter name ODPT’s own 403 names). Pass your own key via _apiKey if you’d rather use your own registration — sign up at https://developer.odpt.org/signup (English: https://developer.odpt.org/en/signup, note: account approval is manual, not instant), then issue a key once logged in.

Coverage: the authenticated host only

ODPT’s production API gates every class behind acl:consumerKey, with no exception — verified live against an unfiltered operator list, station lookups for three operators, and even the RDF-type listing, all HTTP 403 Require acl:consumerKey.. A separate keyless host exists but only ever serves one operator (confirmed live: an unfiltered station query returns 149 rows, all Tokyo’s Toei bureau; filtering to Tokyo Metro returns HTTP 200 with an empty array — a silent-zero success, not real coverage) and is not used here even as a fallback: a keyless 200-with-nothing would make this pack look alive while actually serving nothing for Tokyo Metro, JR East or live status — the three things most callers actually want.

Licence

ODPT publishes this data under its own Public Transportation Open Data Basic License (the licence linked from the data catalog’s Tokyo Metro station/timetable entries). Summarized from the licence text at https://developer.odpt.org/terms/data_basic_license.html (read in full there before building anything that redistributes this data further):

• Data may be used, combined and built on, for-profit or nonprofit, inside a “Deliverable” (an app, dataset or document) that is released to the public.
• Raw data may not be displayed or redistributed outside that Deliverable — no “release, redistribute, publicly transmit, or assign” of the data, its duplicates, or a derivative that would let a third party reconstruct the original. This pack only ever calls the keyed API live, per caller request (a proxy, not a mirror), so it ships under the same proxy-is-not-redistribution basis as the rest of the Pipeworx catalog — nothing here bakes or bulk-downloads ODPT’s dataset.
• A Deliverable must tell its users that ODPT and the data providers make no warranty on accuracy, and must carry its own contact channel so inquiries go to the Deliverable’s operator, not directly to the railway operators.
• Using the data must not create “disadvantage or a bad reputation” for ODPT, its association, or the data providers.

This pack is a live proxy to the keyed ODPT API on a caller’s behalf; it is not itself the Deliverable, and does not speak for how any caller’s own application uses the results.

Traps

• Name resolution costs upstream calls. ODPT has no title-search endpoint — odpt_resolve_station fetches each operator’s full station list and filters client-side. Passing an operator narrows it to one upstream call; omitting it fans out across a default list of major Tokyo operators.
• Operator/railway ids are not obvious strings. odpt.Railway:<operator id>.<line name>, e.g. odpt.Railway:TokyoMetro.Marunouchi or odpt.Railway:JR-East.Yamanote — the pack’s odpt_service_status builds this from a plain line name only when both railway and operator are given; pass the exact id directly if you already have it.
• A station can have more than one id. Stations served by multiple operators/lines (e.g. several lines meeting at one named station) have one odpt:Station row per operator/railway that serves them; odpt_resolve_station returns all of them, not one canonical row.
• Live status changes fast; timetables don’t. odpt_service_status is cached for 60 seconds; the other three tools, which answer from a published schedule rather than a live feed, are cached for an hour.

Tools

• odpt_resolve_station — Find a Japan train station by name, in English or Japanese (“Shinjuku” or “新宿”), and return its ODPT station id(s), operator, railway and coordinates — for looking up Japanese railway/metro stations (
• odpt_station_timetable — Scheduled departure timetable at a Japanese train station (Tokyo Metro, JR East, Toei and other Japan railway operators): destination, departure time, train type and direction, for weekday/Saturday/ho
• odpt_train_timetable — Stop-by-stop scheduled timetable for one specific Japanese train run, by railway and train number: every station it calls at with arrival/departure time. Covers Tokyo Metro, JR East, Toei and other Ja
• odpt_service_status — Live service status (current train information) for a Japanese railway line: normal operation, delays, or suspension, with the operator’s own status text in Japanese and English and when it was last u