Skip to content
FlightPowers
Get key

Integrations

Live flight & hotel data in Cursor

Drop one block into .cursor/mcp.json and Cursor’s agent can query live fares and hotel rates while it writes your travel features: real responses, not guessed schemas.

  • Live Google Flights fares and Booking.com rates, asked for in plain English
  • Google's own price band and a low | typical | high verdict on every fare
  • A date range and a list of destinations in one call, and a round trip priced as one request
  • Hotel rates as a shopper in any country sees them, for rate-parity checks. Searches bill to your own RapidAPI plan
Flights key →Hotels key →All MCP options

Free tier: 10 requests/month. No card to try.

.cursor/mcp.json
{
  "mcpServers": {
    "flights": { "url": "https://flights.flightpowers.com/mcp" },
    "hotels": { "url": "https://hotels.flightpowers.com/mcp" }
  }
}

Restart Cursor. It hits the 401, registers itself, and offers you the sign-in: Add the URL, click Sign in, sign in with Google, and paste your RapidAPI key once on the page that opens. 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" } } } }

Connect

Add to .cursor/mcp.json

  1. 1

    Get a RapidAPI key

    Subscribe on the listing’s pricing tab: Google Flights Live API for flights, Booking Live API for hotels. The free tier needs no card. One key covers both once you subscribe to each listing.

  2. 2

    Add the block to .cursor/mcp.json

    Project-level or global: paste the config above. It registers both servers, flights and hotels, and dropping either entry is fine if you only need one. Nothing secret goes in the file on this path.

  3. 3

    Restart Cursor and sign in

    Cursor registers itself and offers the sign-in: sign in with Google, paste your RapidAPI key once, and the tools appear in the Agent toolbox. The same shape works in any mcp.json-style client. For CI and headless runs, keep the same URL and add an x-rapidapi-key header instead.

Ask it

Five things to say, verbatim

Prompts for a coding agent: each one runs a live call and puts the result to work.

“Call search_oneway_flights for LHR to JFK on October 13 and show me the raw JSON so we can write a parser for it.”
“Fetch live fares for LIS to JFK across November and build a test fixture from the five cheapest days.”
“Add a fareVerdict helper that maps price_range_in_relation_to_other_periods to a badge color, then check it against a live JFK to LHR search.”
“Query search_hotels for Lisbon, October 9 to 12, and generate a TypeScript type from the response.”
“Run find_hotel_by_name for the Rixos Sungate with price_as_seen_from de and jp, three times each, and print the range each market landed in.”

Tool inventory

The four tools in the Agent toolbox

Printed raw on purpose: this page is written to be read by an agent as much as by a person.

search_oneway_flightsflights server

One-way fares with Google’s price band, the low | typical | high verdict, and a buy_link on every result. Takes a single date or a date range, expanded server-side.

search_roundtrip_flightsflights server

Paired-leg round-trip itineraries: one object per option with both legs matched and a combined total_price.

search_hotelshotels server

Destination search over live Booking.com rates, with the site’s own filters: review_score_8, free_cancellation, and the rest.

find_hotel_by_namehotels server

One property by the name a human would type. price_as_seen_from prices it from any market, the rate-parity tool.

Recipes

Seven things to build in Cursor

Each one is a full page: the connect block, the prompt, the exact call it makes, and the response fields your logic reads.

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

Cheapest-date scan

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

Questions, answered plainly

Why give a code editor flight data?
Because the agent that writes your travel feature can also run it. Cursor can fetch a live response, generate types and fixtures from it, and test parsing logic against real data instead of a guessed schema: the response shape it codes against is the one production will see.
Is my key billed to me?
Yes. The MCP servers are bring-your-own-key: Cursor sends your RapidAPI key with each call and usage meters against your own subscription. There is no FlightPowers account and no second bill.
Where does the key live?
In .cursor/mcp.json, as a header value. Treat the file as a secret: keep the project-level copy out of shared repositories, or use the global config instead.
Which plan do I need?
The free tier is 10 requests/month with a hard cap: enough to verify the config, not to develop against. For a development workflow, the $10 PRO plan (2,500 requests/month on flights) is the realistic floor. Every plan includes all of its API’s endpoints.
Does the same config work elsewhere?
Yes. It is a standard MCP server over HTTP. Any client that reads an mcpServers block (or accepts a URL plus headers) connects the same way; only the file location changes.

Elsewhere

The same data in the rest of your stack

ClaudeChatGPTClaude Coden8nOpenClawClaude DesktopSmitheryLangChainZapierMakeRESTRapidAPIApifyAll integrations

Get live flight and hotel data

Live Google Flights and Booking.com data as clean JSON. Free tier on RapidAPI, no card to try.

Flights key →Hotels key →See pricing

Free tier: 10 requests/month. No card to try.