Connect FlightSweeper to Claude Code
Connect Claude Code to the same transaction-safe FlightSweeper tool set while keeping final approval and payment on FlightSweeper.
OAuth recommended · token fallback
Authorize with OAuth when the client environment supports it. Use a revocable 30-day personal token only as an advanced fallback; two tokens may overlap during rotation.
Claude Code users who want careful comparison of flexible dates and trip rules.
Use FlightSweeper to compare live flights for this trip. Preserve quote time, expiry, refund terms, and role disclosure. Use book_flight only after I choose and ask to buy.
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.
OAuth access tokens expire after 10 minutes and refresh tokens rotate. If this environment requires the personal-token fallback, the secret is shown once, expires after 30 days, and can be revoked from Account → Integrations.
A personal token is a compatibility path for headless or restricted environments, not the recommended first setup.
Add https://flightsweeper.com/api/agent/mcp as a remote HTTP MCP server in Claude Code.
Authenticate with FlightSweeper OAuth when your Claude Code environment supports the browser flow.
Use a revocable FlightSweeper personal token only when OAuth cannot run in that environment.
Confirm Claude Code discovers the documented FlightSweeper public tools before the first live search.
Enter passenger and card details only 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.