Book flights from Claude Code
Connect Claude to the same ten transaction-safe FlightSweeper tools and create a ready-to-complete hosted checkout without a second agent round trip.
Bearer-token connection available
Authorize with OAuth when supported, or create a revocable 30-day personal token and copy the generated client configuration. Two personal tokens may overlap during rotation.
Claude Code users who want careful comparison of flexible dates and trip rules.
Use FlightSweeper to compare live flights from LAX to ORD for two adults. Preserve my flexibility rules and ask before creating a trip watch or hosted checkout link.
Setup flow
Every client uses the same Streamable HTTP endpoint and the same ten public tools. Checkout links return directly; persistent watch creation keeps hosted approval.
Personal-token secrets are shown once, expire after 30 days, and can be revoked from Account → Integrations. OAuth access tokens expire after 10 minutes and refresh tokens rotate.
Create a FlightSweeper account, then open Account → Integrations.
Create a Claude Code token and copy it once into the FLIGHTSWEEPER_AGENT_TOKEN environment variable.
Copy the generated Streamable HTTP configuration into your Claude Code MCP settings.
Confirm Claude Code discovers exactly ten FlightSweeper tools before the first live search.
Let Claude return the hosted checkout; review the refreshed total and enter passenger/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.