Connect FlightSweeper to Claude
Add FlightSweeper as a custom Claude connector for live flight comparison and a hosted approval handoff.
OAuth setup supported
Claude 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.
Travelers using Claude on the web who want careful comparison of flexible dates and trip rules.
Use FlightSweeper to compare live flights from LAX to ORD for two adults. Preserve quote time, expiry, refund terms, and role disclosure. After I choose and ask to buy, use book_flight.
Setup flow
Every client uses the same Streamable HTTP endpoint and documented public tool set. The primary book_flight action hides the internal intent and approval stages; 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.
In Claude, open Settings → Connectors and add a custom connector.
Use https://flightsweeper.com/api/agent/mcp as the remote server URL.
Authorize the connector with your FlightSweeper account using OAuth.
Confirm Claude discovers the documented FlightSweeper public tool set before the first live search.
Review the refreshed total and enter passenger and card details only on FlightSweeper.
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.