FlightSweeper
For agent builders

Add travel actions without building a travel company.

One MCP server and API handles search, booking policy, approval, hosted traveler and payment handoffs, booking execution, and canonical booking state.

Connect an agent Choose a client

The execution boundary

The agent owns the conversation and requests explicit travel operations. FlightSweeper preserves proposal evidence, enforces the active mandate, and opens a focused hosted handoff when protected data or human attention is required. Raw traveler and payment credentials never return to the agent.

  • Structured search with total price, currency, quote time, and expiry
  • Private participant intake and opaque traveler references
  • Policy evaluation and proposal-bound approval mandates
  • Hosted traveler and payment handoffs
  • One canonical trip state across every supported agent

One execution layer. Every supported agent.

OAuth is the default for traveler-facing assistants. Developer clients should use OAuth when their environment supports it; revocable personal tokens remain an advanced fallback.

Primary assistants

Connect where you already plan.

ChatGPTOAuth setup supportedClaudeOAuth setup supportedPokeOAuth setup supported
Developer clients

Bring the same backend into your tools.

OAuth recommended · personal token fallback

CodexOAuth recommended · token fallbackCursorOAuth recommended · token fallbackClaude CodeOAuth recommended · token fallbackHermes AgentOAuth recommended · token fallbackOpenClawOAuth recommended · token fallback

OAuth owns the connection.

Your agent opens FlightSweeper sign-in, requests explicit access, and receives a short-lived owner-scoped token. You can revoke the connection from FlightSweeper without rotating a shared secret.

  1. 1Choose your assistant or developer client above.
  2. 2Add the remote server https://flightsweeper.com/api/agent/mcp.
  3. 3Sign in to FlightSweeper, review the requested access, and approve the connection.

Focused travel tools

The same remote MCP server serves every client. It can search live flights, check live flight status, read owner-scoped bookings, and discover uncommon account actions. Writes stay bounded to one resumable flight-booking flow, unpaid-intent cancellation, and hosted human approval. Payment, ticketing, paid-order servicing, and private traveler data stay on FlightSweeper.

https://flightsweeper.com/api/agent/mcp
Open the machine-readable contract
  1. 01search_flights
  2. 02book_flight
  3. 03list_bookings
  4. 04get_booking
  5. 05discover_tools
  6. 06run_advanced_action_tool
  7. 07compare_trip_options
  8. 08get_quote_details
  9. 09refresh_quote
  10. 10get_preferences_summary
  11. 11create_booking_intent
  12. 12cancel_booking_intent
  13. 13request_human_approval
  14. 14get_booking_status