Rome2Rio

Name: Rome2Rio MCP Server
Availability: InStock
Author: Rome2Rio

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Travel2 tools

Plan multimodal journeys — flights, trains, buses, ferries, cars — from an AI agent. Two read tools, no booking, no payment. Anthropic lists it authless, but the endpoint 403s every request so we could not confirm that ourselves.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 8 September 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Rome2Rio via MCP

https://chatgpt-app.rome2rio.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Rome2Rio once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Rome2Rio Tools & Capabilities (2)

get-routes

get-schedules

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

We verified nothing on the wire, and the directory's authless flag is unconfirmed rather than contradicted. Anthropic's snapshot records is_authless true and auth_posture "no_auth". Our bulk probe recorded HTTP 403 and classified the server AUTH-REQUIRED. Both readings are wrong to publish. Every path we tried on chatgpt-app.rome2rio.com returned an identical 5,483-byte Cloudflare "Attention Required" page — the listed endpoint, an invented path, the host root, the .well-known descriptor paths, and /robots.txt, which no MCP server gates behind authentication. Adding an Authorization: Bearer header changed nothing. A refusal that does not discriminate between a real route and a fabricated one is a WAF answering, not a server.
No parameter schemas exist on this page, from any source. We could not read inputSchema, and Rome2Rio's announcement documents the connector for travellers rather than developers. What get-routes and get-schedules accept is described here only as Rome2Rio describes it in prose — origin, destination, dates, budget, one-way or return, price and departure-time filters.
Prices are estimates outside of bookable inventory. Rome2Rio states an exact price appears only where tickets can be booked; elsewhere it shows ranges, some derived from a similar service in another operator's network. An agent quoting a Rome2Rio price as a fare is over-reading it.
Schedules can simply be absent. Rome2Rio names seasonal routes, operator publication windows and missing operator feeds as causes, and states operators can change services at any time. Silence from get-schedules is not evidence that no service runs.
Nothing books, pays or reserves. Rome2Rio holds no bookings or payments and cannot issue refunds or amend dates. Every transaction happens on a partner's site, in your browser, under that partner's terms — Rome2Rio's help centre names Omio, Flixbus, 12Go and GoToGate as examples.
Multi-leg journeys are booked leg by leg. Rome2Rio's help centre carries a dedicated article on why each leg is booked separately. A connector answer describing one door-to-door journey may correspond to several separate purchases from several different providers.
The two published coverage figures disagree. Rome2Rio's site description says 160+ countries; its April 2026 ChatGPT announcement says 240+ countries and territories. Neither document acknowledges the other, and we found no reconciliation.
The connector's own mode list is narrower than the website's. Six modes are named for the connector against ten displayed on the website. Whether tram, taxi, walk, shuttle and towncar reach the connector is not stated anywhere we found.
The announcement post describes an unreleased product. Rome2Rio's Claude post, dated 2026-08-28, is written in the future tense throughout and states the connector was pending Claude's review and approval, promising an update when it is listed. It is now listed in Anthropic's directory, so the post is behind its own subject — its forward-looking wording may not match the shipped behaviour.
The endpoint hostname is unexplained by the vendor. Rome2Rio documents no Claude-specific host and never mentions ChatGPT in its Claude announcement. The origin story here is inferred from the two announcement dates, not stated by Rome2Rio.
No rate limit, quota or fair-use policy is published for this connector by Rome2Rio or in Anthropic's listing. The host sits behind Cloudflare, which is a rate-limiting layer by construction, so absence of a published limit is not absence of a limit.

Frequently asked questions

No. Rome2Rio is a search product with no checkout of its own, and its own site documentation states there is no checkout flow on Rome2Rio and that all purchases happen on third-party operator or booking sites. The connector returns links you follow yourself. Rome2Rio also states it cannot arrange refunds or date changes, because it never holds the booking.

Rome2Rio states the connector will be free for Claude users, and Anthropic's directory records the server as authless. We could not confirm the sign-in posture ourselves, because the endpoint host answers every request with an identical Cloudflare block page, including paths no MCP server would ever gate. The posture here is Rome2Rio's claim plus Anthropic's metadata, not our observation.

Because Rome2Rio shipped a ChatGPT app first. Rome2Rio announced that app in April 2026 and the Claude connector in August 2026, and Anthropic's directory points the Claude listing at the same host the earlier product established. Nothing we found documents a separate Claude hostname, and Rome2Rio never explains the name. Treat it as a naming artefact, not a wrong URL.

Mostly estimated. Rome2Rio's help centre states an exact price appears only where you can book tickets, and that where it cannot give an exact figure it displays a price range instead. It also says prices fluctuate with availability and seasonality, and that some ranges are derived from a similar service in the same country.

Rome2Rio's help centre gives three reasons. The route runs seasonally and the schedule is not released yet, the operator does not publish schedules that far ahead, or Rome2Rio has not been given the timetable by the operator. It advises changing your dates or contacting the transport operator directly when this happens.

Rome2Rio states the connector will show options across flights, trains, buses, ferries, cars and multimodal combinations, depending on the journey. Its help centre lists a wider website set including tram, taxi, walk, shuttle and towncar. The connector wording is narrower than the website's, so treat the six named modes as what Rome2Rio commits to here.

Two, named get-routes and get-schedules. Both names come from Anthropic's directory listing rather than from a handshake we completed, because the endpoint refused every request we made. Rome2Rio's own announcement describes the connector's abilities in prose and never prints a machine tool name, so there is no vendor list to check the two against.

Start with an origin and destination, then add dates, budget or preferences. Rome2Rio's own worked examples are a fastest-route question from Kyoto to Tokyo, an options-under-fifty-euros constraint, and a return trip next weekend. Its schedule examples name flights from Helsinki to Tallinn on specific dates and bus schedules from Paris to Brussels under a price cap.