ChatGPT guide

Connect FlightSweeper to ChatGPT

Use FlightSweeper as ChatGPT's owner-scoped flight search, quote, approval, and booking-state backend without exposing passenger or payment data.

OAuth setup supported

ChatGPT connects to FlightSweeper with OAuth authorization code, PKCE, rotating refresh tokens, and an owner-scoped access token. The client never receives passenger identity or payment data.

Best for

Travelers who want to plan and compare flights in ChatGPT, then approve and pay on FlightSweeper.

Starter prompt

Use FlightSweeper to compare live flights for this trip. Show the all-in total, quote time, expiry, refund terms, and refresh state. Create a booking intent only after I choose.

Setup flow

Every client uses the same Streamable HTTP endpoint and the same nine public tools. Booking intents return canonical state; approval and payment stay hosted.

FlightSweeper publishes OAuth discovery and Dynamic Client Registration. OAuth access tokens expire after 10 minutes, refresh tokens rotate, and the connection can be revoked from FlightSweeper.

1

Open ChatGPT connector settings and add a custom MCP connector.

2

Enter https://flightsweeper.com/api/agent/mcp as the remote server URL.

3

Sign in to FlightSweeper and approve the requested OAuth access.

4

Confirm ChatGPT discovers exactly nine FlightSweeper tools before the first live search.

5

Keep passenger entry, quote approval, and payment on the FlightSweeper-hosted handoff.

Tool permissions

Every client should keep the same transaction boundary: search can happen in the agent, but booking happens after the traveler confirms a hosted checkout page.

Fare-bearing results include all-in total, currency, quotedAt, expiresAt, and refresh state.
create_booking_intent is idempotent and cannot charge or ticket; request_human_approval sends the traveler to FlightSweeper.
cancel_booking_intent applies only to approved, unpaid intents. Paid-order servicing and refunds stay hosted.
Booking status, policy summaries, and opaque traveler summaries are scoped to the authenticated owner.