HasData Google Flights Deals

Google Flights Deals MCP Server

A hosted Google Flights Deals 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

• Prompts and resources

Contents

• What you need
• Quick start
• Example prompts
• Tools
• Errors and failure paths
• Pricing, free tier and limits
• How it compares
• FAQ
• HasData links
• Development
• Contributing
• License

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.

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

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

{

"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

{

"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

{

"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

One tool, 15 credits per successful call.

Find flight deals

hasdata_google_travel_flights_deals_getGoogleFlightsDeals

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.

{

"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=…" } ] }

Prompts and resources

The server exposes 7 resources, one per parameter whose accepted values are a fixed list. Reading one is cheaper than learning the vocabulary from a rejected call, and it costs no credits. Each URI is hasdata://google_travel_flights_deals/ .

The list is served without an API key, so a client can read it before a user has signed up.

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 ca