Book flights from Codex
Configure FlightSweeper's remote MCP server in Codex with an owner-scoped token and keep the final transaction on FlightSweeper.
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.
Codex users who want live flight tools alongside their normal work without autonomous purchasing.
Use FlightSweeper to search a flexible round trip within the next six months. Compare the live options and prepare hosted checkout only after I approve one exact quote.
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 Codex token and copy it once into the FLIGHTSWEEPER_AGENT_TOKEN environment variable.
Copy the generated flightsweeper-connect block into ~/.codex/config.toml.
Use `codex mcp list` to confirm the server and its ten tools before a live search.
Create checkout handoffs directly; approve watches and enter passenger/card data 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.