Skip to content

Guide

The Google Flights MCP in Claude

Published September 1, 2026 · Updated November 7, 2026

Short answer: Add https://flights.flightpowers.com/mcp to Claude as a custom connector (and https://hotels.flightpowers.com/mcp for hotels), sign in with Google, and Claude can search live Google Flights fares mid-conversation. Your first 10 searches each day are free, with no RapidAPI key and no card. For more, paste your own key once: PRO is $10 a month for 2,500 flight searches.

What is the Google Flights MCP?

Google has had no public flights API since QPX Express closed in April 2018, so a "Google Flights MCP" is a server someone else runs that reads Google Flights for your assistant. This guide sets up mine, FlightPowers: a hosted server, so nothing runs on your machine. Its two flight tools return each fare's price, airline, stops, a booking link and Google's own price range for the route when Google shows one. Other travel MCP servers exist, open source and hosted; the travel MCP roundup compares twelve, mine included: three cover hotels only, three get their fares from Kiwi.com, Duffel or Aviasales, two do not say where their fares come from, and four read Google Flights.

What you need

  • Claude on the web or the desktop app, or Claude Code
  • A Google account for the sign-in
  • Optional: a RapidAPI key for the Google Flights Live API and the Booking Live API, once 10 searches a day is not enough. One key covers both once you subscribe to each listing. Flights PRO is $10 for 2,500 searches a month, hotels PRO $10 for 2,000; the free BASIC tier (50 requests a month on flights, 10 on Booking.com) only checks your key works.

Add it to Claude

One click opens Claude's "Add custom connector" screen with the name and the URL filled in:

After Continue, choose ‘Sign in when needed’ (not the pre-selected ‘No sign-in’), then Add. Sign in with Google: 10 free searches a day, no card. More with your own key: PRO $10/month for 2,500 flight searches.

By hand, in Claude on the web or the desktop app: Customize → Connectors → + Add → Add custom connector, paste https://flights.flightpowers.com/mcp (and again for https://hotels.flightpowers.com/mcp), press Continue, choose ‘Sign in when needed’ (not the pre-selected ‘No sign-in’), then Add, and sign in with Google when Claude asks. The Claude connector page has the step list and five prompts to try.

Add it to Claude Code

One line each, from any directory:

claude mcp add --transport http flights https://flights.flightpowers.com/mcp
claude mcp add --transport http hotels https://hotels.flightpowers.com/mcp

Then open /mcp in a session and sign in. claude mcp list prints ✔ Connected when it worked and ! Needs authentication when the sign-in has not happened yet.

Or create .mcp.json in your project root (commit this file, there is nothing secret in it):

{
  "mcpServers": {
    "flights": { "type": "http", "url": "https://flights.flightpowers.com/mcp" },
    "hotels": { "type": "http", "url": "https://hotels.flightpowers.com/mcp" }
  }
}

For user-wide config (applies to all projects), add the same block to ~/.claude.json on Mac/Linux or %USERPROFILE%\.claude.json on Windows.

Going past 10 searches a day

The free searches run on our key and are shared by the flights and hotels servers. To go past them, paste your RapidAPI key once: on the page that opens when you sign in, or later at https://flights.flightpowers.com/connect with the same Google account. That is the only time the key is typed anywhere: it is encrypted before it is stored, only its last four characters are ever shown again, and searches then meter against your own subscription. Disconnect on the connect page deletes it.

The key in a header, for scripts, CI and clients without a sign-in button

A headless run cannot open a browser, so claude -p in a cron job, a CI step, or any client with no sign-in button sends the key in a header. Same two URLs as above, no sign-in step:

{
  "mcpServers": {
    "flights": {
      "type": "http",
      "url": "https://flights.flightpowers.com/mcp",
      "headers": { "x-rapidapi-key": "YOUR_RAPIDAPI_KEY" }
    },
    "hotels": {
      "type": "http",
      "url": "https://hotels.flightpowers.com/mcp",
      "headers": { "x-rapidapi-key": "YOUR_RAPIDAPI_KEY" }
    }
  }
}

Replace YOUR_RAPIDAPI_KEY with your actual key, and treat the file as a credential file. There is one address per server and it serves both paths, so an existing keyed setup keeps working untouched.

The six tools

search_oneway_flights: Live one-way flight prices from Google Flights. Pass a single date or a date range (departure_date_from / departure_date_to), and one destination or several, and the server expands it internally. Each result includes price, price_as_number, price_range_in_relation_to_other_periods (the context field), and a buy_link that opens the itinerary on Google Flights ready to book.

search_roundtrip_flights: Paired round-trip itineraries with both legs already matched. One object per option with a combined total_price, not two lists to cross-join. Takes a return_date or a trip length in nights.

search_hotels: Live Booking.com destination search. Returns ranked properties with price_string, price, review_score, room_type, the hotel's latitude and longitude, and a link. Accepts the same filters the site offers: review_score_8, free_cancellation, and the rest.

find_hotel_by_name: Availability and price for one named hotel. Takes the name a human would type (add the city to disambiguate a chain) and resolves the property internally. Supports price_as_seen_from, a two-letter country code that prices the stay as a shopper in that market would see it, the field rate-parity checks are built on.

search_airbnb: Live Airbnb stays for a destination and dates, read from Airbnb's public search page when you ask. Each stay has a stay total, a per-night price, a rating out of 5, room type, bedrooms, beds, baths and an Airbnb link. It needs its own Airbnb Live API subscription on the same RapidAPI key; the free sign-in searches do not cover it.

compare_hotel_rates: Prices the same stay on Booking.com and Airbnb and returns one row per source: the cheapest total, the median total and how many places were priced. Ratings are out of 10 on Booking.com and out of 5 on Airbnb, and taxes_included is null on Airbnb. It runs on your own RapidAPI key; the free sign-in searches do not cover it. Each source is one billed request on its own subscription.

Example prompts

Ask about a specific date. "Find me a nonstop LHR to JFK flight on March 12 and tell me if the price is any good."

Scan a whole month. "What is the cheapest day to fly Lisbon to New York in February?"

Compare trip lengths. "Round trip from JFK to Lisbon, leaving any day in February, 5 to 7 nights. Which dates are cheapest?" That is 28 departure days at three trip lengths, 84 searches in one call, so it runs on your own key, not on the 10 free a day.

Plan a trip. "I need a round trip JFK to Paris, out April 6, back April 13. What are my best-value options?"

Search hotels. "Find a hotel in Lisbon, March 9 to 12, 2 adults, review score 8+, free cancellation."

Check rate parity. "Price the Rixos Sungate in Antalya for May 5 to 10 as seen from the US, Germany, and Israel."

How it works

The servers are hosted at https://flights.flightpowers.com/mcp and https://hotels.flightpowers.com/mcp. Nothing runs on your machine. After the Google sign-in, the first 10 searches each day run on our key; once you paste your RapidAPI key on the connect page it is stored on our side, encrypted, and used on each call. On the header path Claude sends the key in x-rapidapi-key. Either way, past the free searches, usage meters against your own subscription. Disconnect on the connect page deletes a stored key and cuts off every client using it.

Date ranges and destination lists

Both flight tools accept a date range (departure_date_from / departure_date_to) and several destinations in to_airport (a comma-separated string like "BCN,LIS,ATH" or a list). The origin is one airport per search. The server expands the range and the destinations internally, so a flexible search is one call where the REST API would be a client-side fan-out of one request per date and destination combination. Each combination is one search, and the count comes back in api_usage.

When to use this

Use the MCP servers when you want Claude to search live travel data mid-conversation. The response shape Claude sees is the one production will see. Use the REST API for production traffic and scheduled scans outside Claude.

Ask Claude for a live price

Add the URL, sign in with Google, and ask for a fare: 10 searches a day are free. The paid tiers on your own key are sized for an assistant you use every day.

Free tier: 50 requests/month on flights, 10 on hotels. No card to try.

Docs: the Flights API, the Hotels API and the MCP servers.