Google Flights MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | HasData API key, created free at https://app.hasdata.com |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hasdata_google_travel_flights_getGoogleFlightsA | Get Google Flights Results Searches Google Flights for one-way, round-trip, or multi-city itineraries with passenger mix (adults, children, infants in-seat/on-lap), travel class, bags, max price, sort order (price, duration, emissions, departure/arrival time), stops, include/exclude airlines and connections, time windows, layover duration, and deep-search mode. Returns per-itinerary price, currency, total duration, stops, flight legs with airline, flight number, aircraft, departure/arrival airports and times, CO2 emissions, plus booking and departure tokens for round-trip returns or booking options. Use for travel-planning agents, fare monitoring, corporate travel dashboards, emission-aware trip optimization, and comparing routes and airlines across markets. |
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
With only one tool present, there is no possibility of an agent confusing it with another tool. The lone tool is clearly described as the only way to search Google Flights results.
The single tool name mixes a snake_case provider/domain prefix with a camelCase verb phrase, which is internally inconsistent. Since there is only one tool, there is no broader set of names to establish a consistent pattern, so the score is moderate.
A single tool for a flight-search MCP server is borderline; it is not a trivial tool, but the surface feels thin for a server that could plausibly support fare calendars, route metadata, or booking workflows. The count is acceptable but not well-rounded.
The one tool covers a wide range of search options, including itinerary types, passenger mix, class, bags, price, stops, airlines, time windows, and emissions. For its stated purpose of getting Google Flights search results, it is quite complete, though auxiliary endpoints like airport lookup or flight status are absent.