HasData Google Flights Deals

com.hasdatav1.0.0Updated Oct 5, 2026

A plain-language trip description becomes dated flight deals with prices and booking links.

VerifiedStreamable HTTPWeb executableLocation & LifestyleWeb Search & Scraping

Overview

AI-generated overview

Turns a plain-language trip idea into dated Google Flights deals with fares, typical prices, airlines, stops and booking links.

What it does
Exposes one tool, hasdata_google_travel_flights_deals_getGoogleFlightsDeals, that takes a free-text trip description plus an origin IATA code and returns structured JSON: dated deals with fare, typical price for the route, duration, trip length, stops, operating airline, airports and a Google Flights booking link. It also reports what Google derived from the query, including the departure airport, the date range searched and the price range. Optional parameters pin the destination, trip type, cabin, dates, trip length, stops, maximum duration, maximum price and airline include/exclude lists.
When to use it
Use it when a trip is still being imagined rather than decided: finding where and when to go from a loose description such as a cherry blossom trip or a beach escape. Once the itinerary is fixed, a conventional flight-pricing API is the better fit.
Requirements
A HasData API key, supplied as the HASDATA_API_KEY environment variable for the npm or PyPI stdio launcher, or as the x-api-key header for the hosted endpoint. The remote server needs only an MCP client and network access; the stdio launchers need Node.js or uvx. No Google account is involved.
Before you install
Each successful call spends 15 credits from the connected account; the free tier is 1,000 credits a month, about 66 searches. Failed validation or upstream errors are not billed. Filters such as stops, maxPrice and cabin are only applied when arrivalId pins a destination, and a request that omits it still succeeds with the filters ignored. Dates come from Google unless pinned, so quote the reported date range. The server reads public flight-deal data, carries no passenger data and books nothing.

Installation

In SourceWeft

  1. Open HasData Google Flights Deals in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "google-flights-deals": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=google_travel_flights_deals"
    }
  }
}

README

Google Flights Deals MCP Server

A hosted Model Context Protocol (MCP) server that gives Claude, Cursor, Windsurf and any other MCP client one Google Flights Deals tool. Describe a trip in plain language, such as "cherry blossom in Japan" or "beach escape", and get dated fares from one origin airport with the typical price beside them, the airline, the stops and a booking link, as structured JSON.

1,000 free credits every month, no card required, which is about 66 searches.

https://mcp.hasdata.com/mcp?apis=google_travel_flights_deals

[Glama score] [tool contract] [MCP] [Tools] [npm] [PyPI] [License]

Contents

What you need

An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 66 calls a month at the 15-credit rate. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run and no Google account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/google-flights-deals-mcp on npm and hasdata-google-flights-deals-mcp on PyPI, shown below.

Quick start

The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.

FieldValue
URLhttps://mcp.hasdata.com/mcp?apis=google_travel_flights_deals
TransportHTTP, streamable
Auth headerx-api-key: HASDATA_API_KEY

Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.

Claude Code
bash
claude mcp add --transport http google-flights-deals "https://mcp.hasdata.com/mcp?apis=google_travel_flights_deals" \  --header "x-api-key: HASDATA_API_KEY"
Claude Desktop
json
{  "mcpServers": {    "google-flights-deals": {      "type": "http",      "url": "https://mcp.hasdata.com/mcp?apis=google_travel_flights_deals",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}
Cursor
json
{  "mcpServers": {    "google-flights-deals": {      "type": "streamable-http",      "url": "https://mcp.hasdata.com/mcp?apis=google_travel_flights_deals",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}
VS Code
json
{  "servers": {    "google-flights-deals": {      "type": "http",      "url": "https://mcp.hasdata.com/mcp?apis=google_travel_flights_deals",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}

Example prompts

Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because every successful call costs 15 credits.

I want to see cherry blossom in Japan, flying from LAX. What are the cheapest dates?

One call, 15 credits. Google picks the destinations and the date range from the description.

Beach escape from London in February, nothing over 600 pounds, direct only.

One call, 15 credits. The price ceiling and the stops filter both need a destination pinned with arrivalId, so the agent has to name one or drop the filters.

Same trip but to Tokyo specifically, ten days, business class.

One call, 15 credits. With arrivalId set, the trip length and the cabin become available.

Compare the cherry blossom idea from LAX and from JFK.

Two calls, 30 credits. One origin per call.

Tools

ToolWhat it returns
hasdata_google_travel_flights_deals_getGoogleFlightsDealsDated deals with the fare, the typical price for the route, flight duration, trip length, stops, the operating airline, the airports and a Google Flights booking link, plus the destinations and date range Google derived from the query. 15 credits a call

One tool, 15 credits per successful call.

Find flight deals

hasdata_google_travel_flights_deals_getGoogleFlightsDeals

ParameterTypeRequiredNotes
qstringyesFree-text trip description, from a bare place name to a full sentence
departureIdstringyesOrigin as a three-letter uppercase IATA code, for example LAX
arrivalIdstringPins the destination instead of letting Google choose. Every filter below needs it
typestringroundTrip (default) or oneWay
travelClassstringeconomy, premiumEconomy, business or first
outboundDatestringAn exact date, or a window as 2026-12-01,2026-12-10
returnDatestringSame spelling as outboundDate, and required alongside it
travelDurationstringPreset length, week, weekend or twoWeeks
tripLengthstringLength in days, instead of returnDate or travelDuration
stopsstringnonStop, oneStopOrFewer or twoStopsOrFewer
maxDurationnumberCeiling per flight in minutes
maxPricenumberCeiling in the currency of the request
includeAirlines / excludeAirlinesstringOne or the other, never both

The filters are the thing to get right. All of them require arrivalId. A prompt that asks for direct flights under a price cap while letting Google pick the destination is asking for two things that cannot be combined, and the API says so with a 422 naming the offending pair. Pin a destination or drop the filters.

searchInformation reports what Google made of the query: the departure airport in full with its city and coordinates, the dateRange it settled on, the priceRange it found and the airlines involved.

json
{  "searchInformation": {    "query": "cherry blossom in Japan",    "departure": { "airport": "LAX", "city": "Los Angeles", "country": "United States" },    "dateRange": { "from": "2027-03-01", "to": "2027-04-30" }  },  "flightDeals": [    {      "outboundDate": "2027-03-01",      "returnDate": "2027-03-08",      "price": { "value": 960, "currency": "USD" },      "typicalPrice": { "value": 1335, "currency": "USD" },      "discountPercent": 28,      "durationMinutes": 1320,      "tripLengthDays": 7,      "stops": 1,      "airlineCode": "CX",      "airline": "Cathay Pacific",      "multipleAirlines": false,      "departureAirport": "LAX",      "arrivalAirport": "HIJ",      "destination": { "city": "Hiroshima", "country": "Japan", "highlight": "Peace Park Memorial & Shukkei-en garden" },      "bookingLink": "https://www.google.com/travel/flights?tfs=…"    }  ]}

Errors and failure paths

Your client almost never sees an HTTP error code from a tool call. The MCP layer answers 200 and puts the failure inside the result, with isError set to true and the reason as text.

discountPercent is the exception, not the rule. Across 351 deals measured on 2026-10-05 it was present on 109 of them. Where it appears it matches the gap between price and typicalPrice to within a rounding step, and where it is absent that gap ran from 4% to 15%, so Google appears to publish the field only past a threshold of its own. typicalPrice was on every deal, so compute the comparison yourself rather than reporting "no discount" because the key is missing.

airline and airlineCode go missing together. In that same sample 269 deals named a carrier and 82 did not, and the split is exactly the multipleAirlines flag: every deal that set it to true omitted both fields, every deal that did not carried both. Read the flag before reporting a carrier, and say "several airlines" rather than leaving the field blank.

A filter without arrivalId is rejected before it runs. The API answers 422 with rule: "requiredIfExists" naming both arrivalId and the filter that triggered it, and nothing is billed. All eleven filters behave this way, so the failure is loud and cheap rather than silent.

Dates are what Google chose unless you pinned them. searchInformation.dateRange is the range it searched, which can be months away from today. Quote it when presenting prices, because a fare for next March is not a fare for next month.

Each successful call spends credits from the connected account. Neither a 422 from validation nor a 400 from upstream is billed, measured by reading the balance either side of a call.

Pricing, free tier and limits

The Google Flights Deals tool costs 15 credits per successful call, the same as the Google Flights API. The number of deals returned does not change the price.

The free tier is 1,000 credits every month with no card, which is about 66 searches.

Paid plans start at $59 a month for 200,000 credits, which is about 13,000 searches. The unit price falls on larger plans. Current numbers are on the plans page.

How it compares

Google Flights APIThis server
InputAn origin, a destination and datesA sentence, with the destination optional
Who picks the destinationYouGoogle, from the description
Who picks the datesYouGoogle, unless you pin them
Best forA trip someone has already decided onA trip someone is still imagining

The two sit next to each other rather than competing. Use this one to find where and when, then the Google Flights API to price the itinerary once the trip is decided.

FAQ

Do I need a Google account?

No. The only credential involved is your HasData key.

Why were my filters ignored?

They almost certainly went out without arrivalId. Every filter on this tool needs a pinned destination, and a request that omits it still succeeds.

Can I search from several origins at once?

No. departureId takes one airport, so comparing origins means one call each.

How far ahead does it search?

As far as Google decides from the query. Read searchInformation.dateRange rather than assuming the next few weeks.

Is HasData affiliated with Google?

No. HasData is an independent web data provider and is not affiliated with, endorsed by or sponsored by Google. All trademarks belong to their owners.

Compliance and personal data

The server reads the public Google Flights deals interface. It carries no passenger data and books nothing.

HasData links

Product page and request builderGoogle Flights API
Endpoint documentationGoogle Flights Deals API docs
Server documentationMCP server docs
Every tool in one serverHasData/hasdata-mcp
Client walkthroughsMCP clients and integrations
Plans and credit costsPlans and credit costs

Development

bash
npm installnpm test

The tests in test/ assert the tool contract, the part that can break without a commit here. They check that ?apis=google_travel_flights_deals returns the one expected tool, that its name and required parameters have not changed, that it carries a description, and that a real search still returns flightDeals with the documented fields.

Contributing

The parameter table and the sample above were read from the live schema and from a real call rather than from documentation. A correction is welcome when a field or a failure mode has changed. Open an issue with the response you saw.

License

MIT

Source: README.md at commit 4652cca

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 5, 2026