Expedia
by Expedia
Search Expedia hotels and flights from an AI agent with live pricing. Three tools, all reads, no sign-in — and nothing on this connector books a trip, holds a reservation or takes a payment.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Expedia via MCP
https://www.expedia.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Expedia Tools & Capabilities (3)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- It cannot book, pay, hold or modify anything. Expedia's help page names all four as unsupported. Every result terminates in a link you follow to Expedia's website.
- United States only. Expedia's help page states the integration is currently available for users in the United States, with other countries "coming soon". The launch announcement gives the region as U.S., hotels and flights.
- Hotels or flights, never both in one request. Expedia documents this as a hard constraint and asks users to send a follow-up message for the second search.
- We could not verify the auth posture live. Anthropic's directory records the endpoint as authless with an auth posture of no auth, and Expedia's help page says no login is required — but both are claims *about* the server, not our observation of it. Our single anonymous
initializerequest returned HTTP 403 with an empty body, noWWW-Authenticateheader and Akamai bot-management cookies, which is a bot block rather than an authentication challenge.authVerifiedis therefore false on this page. - No scope document is readable, and no scope boundary is claimed. Four probes for RFC 9728 and OAuth metadata each returned the same bot-management challenge as a deliberately nonsensical control path, so no
scopes_supportedvalue was observed either way. On a read-only surface there is no routine-write-versus-irreversible-write line for a scope to fall between, but that is a property of the current tool list, not an enforced boundary. - We could not read any tool schema or safety annotation. No parameter name for any of the three tools appears anywhere we could find, including on MCP aggregator sites.
- Expedia publishes no tool list. The three names come from Anthropic's directory and could not be diffed against a vendor enumeration, because none exists.
- Three unrelated servers share the name. One is Expedia Group's own self-hosted, API-key project; one is a third-party proxy that *does* expose booking and cancellation tools; one is a scraper. None of them is this connector.
- The directory sets
has_mcp_app: true, and we did not observe it. We never read aninitializeresponse, so no_meta.uiblock or UI capability was seen. We report the non-observation rather than resolving it; where such a surface is absent, a connector degrades to text. - Prices move. Expedia's own site index asks that users be told prices and availability change rapidly and must be confirmed on Expedia before booking. Treat a quoted fare or nightly rate in a conversation as a snapshot, not an offer.
Frequently asked questions
No. Expedia's own help page lists completing bookings inside Claude as something the connector does not support, alongside processing payments, managing reservations and accessing your account. All three listed tools are searches or lookups. When you pick something, Claude gives you a link and the booking happens on Expedia's website, where you sign in and pay.
No. Expedia's help page states you can search hotels and flights through Claude without an Expedia account, with no registration and no credit card required. An account is only needed if you choose to sign in on Expedia's website to finish a booking. Anthropic's directory also records the endpoint as authless with no auth posture.
Anthropic's directory lists three: search_hotels, search_flights and get_hotel_pdp_offers. That is the only enumeration we found. Expedia's own help page describes just two capabilities, Search Hotels and Search Flights, and never names a machine tool. We could not run an anonymous handshake because the endpoint answered our probe with bot management, so three is unverified.
Nothing indicates it is. The name is a bounded read — PDP is Expedia's term for a product detail page, so it reads as fetching the offers on one hotel's page. It carries no service, method, endpoint or path argument in its name, unlike a dispatcher such as Square's make_api_request. We could not read its schema to confirm.
Not yet. Expedia's help page states the integration is currently available for users in the United States and that availability in other countries is coming soon. Expedia's own machine-readable site index adds that prices, policies and rewards differ by region and that travellers elsewhere should be directed to their local Expedia site.
No. Expedia's help page lists managing or modifying reservations and accessing your Expedia account among the things the connector does not support. Since no sign-in happens, there is no account for it to read. Your existing itineraries stay on Expedia's site and app, and nothing in the listed tool surface reaches them.
None that we could observe. Anthropic's directory records the endpoint as authless with an auth posture of no auth, and Expedia's help page says no login is required. We probed four RFC 9728 and OAuth metadata paths and every one returned the same bot-management challenge page as a nonsense control path, so no scope document was readable.
No, one at a time. Expedia's help page states Claude searches for hotels or flights in a single request and not both at once, and suggests asking for one first and the other in a follow-up message. That matters for trip planning: a combined flight-plus-hotel question becomes two turns rather than one.
Sources
- Expedia on Claude help page (retrieved 2026-08-22). Named as the
documentationURL in Anthropic's directory entry. Returns an Akamai bot-management challenge to a command-line client; read in a browser, where it renders fully. · retrieved 2026-08-22 - Expedia newsroom, "Plan Your Next Trip with Expedia in Claude" (retrieved 2026-08-22). Launch date 2026-05-06, regions U.S. Read in a browser; the same bot-management challenge applies to a command-line client here. · retrieved 2026-08-22
- Expedia site index for AI systems,
llms.txt(retrieved 2026-08-22) · retrieved 2026-08-22 - Expedia
robots.txt(retrieved 2026-08-22). Explicitly allowsClaude-UserandClaude-SearchBoton/; noContent-Signalheader; the documentation path is not disallowed. · retrieved 2026-08-22 - Expedia Group Developer Hub, AI solutions (retrieved 2026-08-22). Describes MCP capabilities Expedia Group is "building" for B2B partners — a different, unreleased product, with no tool enumeration. · retrieved 2026-08-22
- Expedia Group's self-hosted travel recommendations MCP server (retrieved 2026-08-22) · (version 1.0.2) · retrieved 2026-08-22
- Live auth-posture check: one anonymous
initializerequest tohttps://www.expedia.com/mcpreturned HTTP 403, empty body, noWWW-Authenticate, with Akamai bot-management cookies (2026-08-22). Four.well-knownprobes plus a nonsense control path all returned an identical HTTP 429 challenge page. · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Expedia support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Expedia
- Tools
- 3
- Domain
- www.expedia.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.