Connect FlightSweeper to OpenClaw
Add FlightSweeper as a Streamable HTTP server in OpenClaw with OAuth and the documented public-tool allowlist.
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.
OpenClaw users who want live flight search without granting an agent autonomous purchase authority.
Use FlightSweeper to search live one-way or round-trip flights for this goal. Show quote freshness and do not create checkout until I choose and approve the exact offer.
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 Streamable HTTP server in your OpenClaw gateway configuration.
Authorize OpenClaw with your FlightSweeper account using OAuth.
Use a revocable personal token only if OAuth cannot run in that environment.
Keep parallel FlightSweeper tool calls disabled and retain the generated public-tool include filter.
Complete final fare review, traveler entry, and payment 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.