Recipe · Flights API
Cheapest-date scan with Cursor
On the MCP server the tool accepts a date RANGE and expands it internally: one call, not thirty. The agent gets a fare per day and answers with the cheapest date and how much picking it saves. Over REST, the same scan is a parallel burst of per-date requests, which the rate limits (150–500/min by tier) exist for; an Apify run takes one departure date, so the scan is one run per date.
Free tier on RapidAPI. No card to try.
Step 1 · Connect
Add to Cursor
Cursor hits the 401, registers itself, and offers you the sign-in (manage it on the Customize page in the sidebar): Add the URL, click Sign in and sign in with Google: the first 10 searches a day are free, and you paste your RapidAPI key once on the page that opens when you want more. One URL, whichever way you connect. The same shape works in any mcp.json-style client. For scripts, CI and clients without a sign-in button, keep the same URL and add a header instead: { "mcpServers": { "flights": { "url": "https://flights.flightpowers.com/mcp", "headers": { "x-rapidapi-key": "YOUR_RAPIDAPI_KEY" } } } }
{
"mcpServers": {
"flights": { "url": "https://flights.flightpowers.com/mcp" }
}
}Bring your own RapidAPI key: every request is billed to your own subscription, never ours.
Step 2 · Ask it
The prompt
Verbatim: paste it, or anything shaped like it. The agent maps it to the call below.
“What is the cheapest day to fly LIS to New York in June?”
Step 3 · Under the hood
What the agent calls
No glue code: the agent reads the tool schema, picks the tool, and fills these parameters from your prompt.
// search_oneway_flights
{
"from_airport": "LIS",
"to_airport": "JFK",
"departure_date_from": "2027-06-01",
"departure_date_to": "2027-06-30",
"limit": 5
}Step 4 · Read the response
Fields your logic reads
The response is flat JSON. These are the fields this recipe branches on, with what each one means.
departure_datestring (YYYY-MM-DD)The date this fare applies to, the axis a date-range scan pivots on.
pricestringThe fare as Google Flights displays it: “$56”. The numeric twin price_as_number rides alongside for sorting and arithmetic.
price_range_in_relation_to_other_periods"low" | "typical" | "high" | nullGoogle’s verdict on the current fare against that band, the single field alerting, ranking, and “book now” logic branch on.
Questions, answered plainly
- Is my key billed to me?
- Yes. The MCP server is bring-your-own-key: Cursor sends your RapidAPI key with each call and usage meters against your own subscription on RapidAPI. There is no FlightPowers account and no second bill.
- Does this need a server of mine?
- No. The MCP servers are hosted at flights.flightpowers.com and hotels.flightpowers.com: you add a URL to Cursor, not a deployment.
- What does it cost?
- The Google Flights Live API's free tier is 50 requests/month with a hard cap: enough to verify your key works, not to evaluate. The PRO plan is $10/month for 2,500 requests, and every plan includes every endpoint. Budget one request per date scanned: a 30-day sweep meters as 30 requests.
Also works with
Cheapest-date scan, elsewhere in your stack
More recipes
More to build in Cursor
One-way flight search
Flights API · search_oneway_flights
Round-trip search
Flights API · search_roundtrip_flights
Price-insights check
Flights API · search_oneway_flights
Hotel search
Hotels API · search_hotels
Rate-parity check
Hotels API · find_hotel_by_name
Fare-alert cron
Flights API · search_oneway_flights
Get live flight and hotel data
Live Google Flights and Booking.com data as clean JSON. Free tier on RapidAPI, no card to try.
Free tier: 50 requests/month. No card to try.
Docs: the Flights API and the MCP servers.