Claude Adds In-Chat Flight Booking via Otto and LetsFG

Otto Travel shipped a book_flight tool in Claude’s connector directory in June 2026, and that one line separates it from most travel integrations. Built by Otto Trip, Inc. and marked Anthropic verified, the connector handles flight and hotel search, car rentals, reservation lookups, and cancellations through plain-language requests. You describe the trip. Claude returns a shortlist. You confirm, and the reservation closes in the thread.

Otto’s own setup guide, published September 4, 2026, spells out the limits. Flights book one traveler at a time. Pricing is USD only, at public rates. No checkout page opens.

LetsFG is the second service with a working purchase path. It connects over the Model Context Protocol, either from the connector directory or by adding its remote MCP server, using an authorization flow with no local app to install. After you pick an itinerary, Claude gathers passport-level traveler details and hands the request to a LetsFG booking agent, which buys the ticket from the seller.

Payment runs on the provider’s terms. LetsFG’s documentation says the quoted price is held on the card, not charged. Capture happens only once a real airline PNR exists. A failed booking releases the hold. The company puts the full cycle at four to eleven minutes.

Expedia’s connector landed earlier, in May 2026, and exposes three tools: search_flights, search_hotels and get_hotel_pdp_offers. No booking tool appears on that listing. Same directory, different ceiling.

Search Is Not Checkout

Flight search inside an AI assistant is old news. Expedia proved that in May. What changed is the last step the part where money moves.

That distinction is the whole story, and it gets flattened constantly. A connector that installs in two minutes does not mean a flight buys itself in one click. You still choose the itinerary, supply traveler details, and authorize payment under whatever rules the provider wrote. Otto needs an Otto account and an authorization step. LetsFG asks for a card at first booking. Managed business workspaces add another gate: Otto’s guide notes that an owner has to add the connector before anyone on the team can authorize it.

The confirmation layer sits with Claude itself. Its Help Center states that the assistant checks with you before a connected app books, buys or reserves anything, and that it “doesn’t transact on its own” per Anthropic’s support documentation. Final sign-off is yours. claude

For frequent business travel, Otto’s post-booking behavior is the stronger pitch. It stores confirmation numbers, flight times, hotel addresses and reservation details, supports eligible changes and cancellations, and the company says it monitors prices on eligible refundable fares and flags drops.

The booking layer belongs to third parties, not Anthropic. There is no first-party travel service. Which means the same prompt produces different results depending on what you connected: Otto gives you a confirmed ticket, Expedia gives you a list.

Where This Goes Next

The missing numbers are the interesting ones. None of the published sources show how many Claude users have completed a purchase through these connectors, or how reliably bookings succeed across providers. Watch for two signals: provider-level success rates, and any move by Anthropic to pull booking in-house instead of leaving it to the connector market.

Sources: Claude’s official connector directory, Otto’s connection guide (September 4, 2026), LetsFG’s Claude setup documentation, Claude Help Center, Claude’s official Expedia connector listing