Book flights from Cursor
Use one remote FlightSweeper MCP server from Cursor without giving the coding agent passenger or payment data.
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.
Cursor users who want their active AI workspace to help plan a real trip.
Use FlightSweeper to find live one-way flights for my trip. Include total price, quotedAt, expiresAt, and whether refresh is required. Never request passenger or card data here.
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 Cursor token and copy it once into the FLIGHTSWEEPER_AGENT_TOKEN environment variable.
Copy the generated server entry into Cursor's mcp.json without adding account or payment credentials.
Confirm that Cursor discovers exactly ten tools before the first live search.
Open the returned hosted URL for final fare review, passenger entry, complete pricing, and payment.
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.