Connect FlightSweeper to Cursor
Use one remote FlightSweeper MCP server from Cursor without giving the coding agent passenger or payment data.
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.
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 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 MCP server in Cursor's mcp.json.
Authorize Cursor with your FlightSweeper account using OAuth.
Use a revocable personal token only if OAuth cannot run in that environment.
Confirm that Cursor discovers the documented public tool set 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.