Book flights from your AI.
Tell FlightSweeper the trip once. It searches live fares, watches your rules, and opens one secure page when you are ready to approve and pay.
The secure boundary
Your AI searches, compares, refreshes, and prepares checkout. You approve the exact request, review the complete total, enter passenger information, and pay on a FlightSweeper-hosted page. No public tool accepts card data, transfers money, issues tickets, cancels orders, or starts refunds.
- Live Duffel-backed fares with total price, currency, quote time, and expiry
- Exact or flexible date, airport, duration, and destination rules
- Opaque traveler IDs and non-PII aliases only—never passenger details
- Price and availability rechecked before payment
- One account shared across FlightSweeper web and supported AI clients
One server, five client guides.
OAuth and personal-token connections are available today. OAuth-capable clients use authorization code with PKCE; every client can use a revocable personal token.
Booking from Claude itself? Add the connector.
The guides above are for coding agents that use a personal token. To book from Claude on the web or in Cowork, add FlightSweeper as a custom connector:
- 1In Claude, open Settings → Connectors → Add custom connector.
- 2Use the server URL
https://flightsweeper.com/api/agent/mcp, and under Advanced settings set the OAuth Client ID toclaude-web(leave the secret blank). - 3Click Connect, sign in to FlightSweeper, and Approve — then ask Claude to find you a flight.
Exactly ten tools
The same remote MCP server serves every client. Higher-risk preference editing, traveler editing, watch management, cancellation, refunds, and support stay on the web.
https://flightsweeper.com/api/agent/mcp- 01search_flights
- 02compare_trip_options
- 03get_quote_details
- 04refresh_quote
- 05create_trip_watch
- 06list_trip_watches
- 07get_trip_watch_status
- 08get_preferences_summary
- 09create_checkout_link
- 10get_booking_status