Claude Rome2Rio connectorWhat Claude can look up for your trips with Rome2Rio.
The Claude Rome2Rio connector exposes 2 tools: 2 read, 0 write. One compares the ways to get from A to B, the other looks up timetables for a specific date. Below: what Claude brings back, what stays out of reach, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when you plan a trip in chat
No more opening a route planner, typing two cities and juggling tabs. You ask Claude in the conversation, it queries Rome2Rio for you and comes back with door-to-door options: travel time, transport modes, estimated prices and a map of each route. Per the publisher, both tools only look up travel information.
Pick between rail, coach and plane. When nothing is decided yet, get-routes lines up as many as four transport modes, each with duration, an estimated price and a map, so the comparison happens in one place.
Find the right departure on a given day. Once the travel date is fixed, get-schedules searches dated timetables for one mode at a time and returns carriers, departure and arrival times, trip length and number of stops.
Sketch a return trip. Ask for a round trip without dates and, per Rome2Rio, the outbound defaults to today and the return to a week later. Correct the dates if that's not your plan.
What Claude won't do here: suggest a rental car, a bike route or a cruise, or find an on-demand ride. Despite the word "book" in the publisher's wording, no tool takes a booking. And nothing runs in the background: no alert fires when a fare drops. That kind of hands-off monitoring is a job for an automation tool, a different line of work; the Integrations page covers that side, and every other connector is listed under Claude connectors.
The vocabulary in one minute
Five words you'll run into while adding Rome2Rio.
- Connector
- The link you set up once between Claude and an outside service, so Claude can use it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs on its own; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, when it shows one: that's where you grant access, once per person, and where it can be taken back.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it's what lets an assistant like Claude talk to an outside service.
Add Rome2Rio to Claude in three steps
- 01
Find Rome2Rio
In Claude's settings, open Customize, then Connectors, and look for Rome2Rio in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization first.
- 02
Start the connection
Click Connect on the connector's row. If the service opens a window of its own, follow it through. A connection that breaks later is fixed with Disconnect and a fresh Connect.
- 03
Read before you confirm
If an authorization screen appears, read it before you approve: it belongs to the service, not to Claude, and it sets what the access covers. After that, just ask your travel question in the conversation.
The 2 tools of the Claude Rome2Rio connector
Rome2Rio gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Two tools, both flagged as read-only by Rome2Rio's own server. Names stay as Claude shows them, in English.
- 2 read
What Claude looks up (2)
2 toolsTwo route and timetable lookups that leave everything as it was.
get-routes
Searches the different ways to get from an origin to a destination and lays out as many as four modes side by side, with duration, an estimated fare and a map. The publisher's description names train, bus, ferry, car and flight.
get-schedules
Pulls the departures for a route on a given date and time: carriers, prices, departure and arrival times, trip length and number of stops. Only transport scheduled ahead is covered, one mode per search.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it would take on an account for you. Here, the publisher presents both tools as lookups.
Rome2Rio's server marks get-routes and get-schedules as read-only and non-destructive. No source describes a specific confirmation for either one, so Claude's default rule is the one that applies. On a Team or Enterprise workspace, owners decide whether members can let certain actions through without being asked each time, and they can limit a connector for the whole organization. Nobody overrides that setting from their own account.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, that information isn't published anywhere.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member can use it. For Rome2Rio's current status, its sheet in the official directory is the reference.
Where Rome2Rio stops inside Claude
A connector isn't an automation. Claude calls these two tools while it answers you: nothing kicks off when a timetable shifts or a fare moves.
Everything this page says about the tools comes from Rome2Rio's own server. Neither Claude's help center nor Anthropic's docs have a page for this connector, and the publisher's blog post couldn't be read when this page was written. The directory's partner badge isn't a security audit either. Anthropic says so on every sheet: it doesn't choose the tools a publisher exposes and doesn't guarantee they behave as described.
Need help connecting Rome2Rio to Claude?
A person reads every message.
