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
} |
| 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 destinations and 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 |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of an agent confusing it with another tool in the set. Its single purpose — fetching Google Flights deals from a natural-language trip description — is unambiguous.
With a single tool there is no cross-tool pattern to compare, but the name itself is a verbose auto-generated composite that embeds camelCase ('getGoogleFlightsDeals') inside a snake_case namespace prefix. It is readable but not a clean, predictable convention.
One tool is borderline thin even for a narrow API-wrapper server. The endpoint is rich (many filters), but a lone tool offers no room for adjacent operations such as airport/location lookup or deal detail retrieval.
The tool covers the core deals-search workflow with extensive filters, dates, pricing and booking links, which is good for the stated purpose. However, there are no supporting operations (e.g., resolving origins, retrieving deal details beyond the link, or alerting hooks), leaving some dead ends for agents.