Connect Japan Transit Data (ODPT) to Copilot Studio
Query Japan Transit Data (ODPT) directly from Copilot Studio. 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 Copilot Studio
- 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 Copilot Studio with your work account, create a new agent (or open an existing one), and in the Build tab choose Tools → + → Add → Model Context Protocol (MCP) in the right panel.
- 3
In the Add MCP server form, enter "Arlet" as the Server name, https://mcp.arlet.dev/mcp/ as the Server URL, choose OAuth 2.0 for Authentication and "Dynamic (detected)" for Configuration type, then click Add. No Client ID / Secret is needed.
- 4
On the Select a connection screen, choose Create new connection → Create, then sign in with Google on the Arlet authorization screen and click Allow. Click Add to attach the tool to the agent, then Publish to use it from Microsoft 365 Copilot.
Requires a Microsoft work account and a Copilot Studio license (or trial). MCP is available only for agents using generative orchestration and not in Copilot Studio in Teams.