Connect Japan Transit Data (ODPT) to Gemini Enterprise
Query Japan Transit Data (ODPT) directly from Gemini Enterprise. Arlet links the two through one MCP connection and takes care of API keys.
This server connects your AI client to the Open Data Center for Public Transportation (ODPT), operated by the Association for Open Data of Public Transportation in Japan.
Two kinds of data are covered:
1. GTFS feeds (101 of them) that ODPT distributes for bus, rail and ferry operators. This is the important complement to the GTFS data repository (gtfs-data.jp), which is mostly community buses outside the big cities: through ODPT you also get Kyoto city bus and subway, Tokyo Metro, Toei subway, Tsukuba Express, Tokyo Rinkai, Iyotetsu bus, Sendai municipal bus and around twenty ferry operators. Search feeds by name or mode, find stops, then get departures for a specific date resolved against the feed's service calendar. 2. Realtime and reference APIs: rail station search, station departure timetables by direction and day type, live train service information (delays, suspensions), operator lists, and airport departure/arrival flight information.
Notes: a free developer registration at developer.odpt.org issues the access token (consumer key), which stays in your own Arlet environment variables. Data licences are set per provider (most are the Public Transportation Open Data Basic Licence or CC BY 4.0), and every response includes the attribution and a reminder to check the provider's licence. What your key can access follows the permissions ODPT grants to your account.
How to connect Japan Transit Data (ODPT) to Gemini Enterprise
- 1
In the Arlet dashboard, open Data tools, find Japan Transit Data (ODPT), set the API key issued by Japan Transit Data (ODPT) and switch it on.
- 2
Sign in to Gemini Enterprise with your organization Google account and open the gear icon at the bottom left → Connectors → Add MCP Server.
- 3
In the MCP info tab, enter https://mcp.arlet.dev/mcp/ as the Server URL and "Arlet" as the Name. In the Auth tab, enter the OAuth settings from the Arlet docs (Authorization URL / Token URL / Client ID / Client Secret / Scopes) and click Add.
- 4
In the connector list on the chat screen, click Connect on Arlet, sign in with Google and authorize. Arlet can then be enabled with the toggle.
Adding custom connectors (MCP) requires a Gemini Enterprise subscription and is not available in the consumer Gemini app. See the docs for the values to enter in the Auth tab.