Google Flights Deals MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | Your HasData API key from the dashboard, sent as the `x-api-key` header. Free to create with no card; the free tier covers about 66 calls a month at the 15-credit rate. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| completions | {} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hasdata_google_travel_flights_deals_getGoogleFlightsDealsA | Get Google Flights Deals Results Turns a plain-language trip description ("I would like to see cherry blossom in Japan", "beach escape", "fireworks festival in Hong Kong") into flight deals from one origin airport, with Google's AI choosing the destinations and travel dates. Each deal carries outbound and return dates, price, flight duration, trip length in days, number of stops, operating airline, departure and arrival airports, and a direct Google Flights booking link; typical price with the discount against it, and a destination description with a photo, come back only for searches Google shaped itself. Also returns the date range Google derived from the query. Filters cover trip type, cabin class, stops, dates, trip length, price and duration ceilings, airlines and party size. Use for inspiration-driven travel search, seasonal and event-based fare discovery, deal alerting, and travel-content generation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| google_travel_flights_deals_type | All 4 accepted values of `type` (Flight type. Requires `arrivalId`. - `1` / `roundTrip` — round trip (default) - `2` / `oneWay` — one way A one-way deal carries no `returnDate` and no `tripLengthDays`.) |
| google_travel_flights_deals_travelClass | All 8 accepted values of `travelClass` (Travel class. Requires `arrivalId`. - `1` / `economy` — economy (default) - `2` / `premiumEconomy` — premium economy - `3` / `business` — business - `4` / `first` — first Fares climb steeply: on LAX-NRT the same search ran $730 in economy against $2882 in business.) |
| google_travel_travelDuration | All 6 accepted values of `travelDuration` (Preset trip length. Requires `arrivalId`. Cannot be combined with `returnDate` or `tripLength`. - `1` / `week` — about a week (6-8 days) - `2` / `weekend` — a weekend (2-3 days) - `3` / `twoWeeks` — about two weeks (13-15 days) Pairs with `outboundDate` to limit the departure period. Ignored when `type` is `oneWay`.) |
| google_travel_flights_deals_stops | All 6 accepted values of `stops` (Maximum number of stops. Requires `arrivalId`. Omitted, any number is allowed. - `1` / `nonStop` — direct flights only - `2` / `oneStopOrFewer` — at most one connection - `3` / `twoStopsOrFewer` — at most two connections A route with nothing at that depth returns an empty `flightDeals` array, not an error — `nonStop` on a route without a direct flight is a valid, empty answer.) |
| google_travel_gl | All 245 accepted values of `gl` (The two-letter country code for the country you want to limit the search to.) |
| google_travel_hl | All 159 accepted values of `hl` (The two-letter language code for the language you want to use for the search.) |
| google_travel_currency | All 71 accepted values of `currency` (Parameter defines the currency of the returned prices) |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of overlap or misselection. Its purpose is clearly stated as retrieving Google Flights deals.
With a single tool, consistency across a set cannot be meaningfully evaluated. The name combines a long snake_case vendor prefix with a camelCase operation suffix, which is readable but not a clean, predictable convention.
One comprehensive tool can cover a single read-only deals endpoint, but the server feels thin. There are no companion tools for airport resolution, search variants, or booking handoff.
The tool supports rich filtering and returns detailed deal data, covering the core discovery workflow well. It lacks any booking or ancillary lookup operations, but those are arguably outside the stated deals-search scope.