Google Flights MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GFLIGHTS_PROXY | No | HTTP(S) proxy for the Google backend | |
| SERPAPI_API_KEY | No | Enables the SerpAPI `google_flights` backend: a paid/free-tier API, more robust than scraping | |
| GFLIGHTS_BACKEND | No | `google`, `serpapi`, or `auto` (Google first, SerpAPI as fallback when a key is set) | auto |
| GFLIGHTS_MAX_SCAN | No | Max days a single `find_cheapest_dates` call may scan | 14 |
| GFLIGHTS_CACHE_TTL | No | Seconds identical searches are cached | 900 |
| GFLIGHTS_MIN_INTERVAL | No | Minimum seconds between upstream requests | 1.5 |
| GFLIGHTS_CONSENT_COOKIE | No | SOCS cookie value for EU consent; set to your own value or an empty string to send nothing | built-in |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_flightsB | Search flights between two airports on a given date (one-way or round-trip). |
| find_cheapest_datesA | Find the cheapest day to fly within a date range (one search per day, max 14 days). |
| compare_airportsB | Compare the cheapest fare across several origin/destination airport combinations (max 6). |
| find_airportB | Look up IATA airport codes by city or airport name (offline). |
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 4 tools
The four tools are mostly distinct by scope: find_cheapest_dates scans a date range, compare_airports tests multiple airport pairs, search_flights handles a single date, and find_airport is an offline code lookup. The only mild overlap is that find_cheapest_dates and search_flights both return fares, though their descriptions clearly separate date-range scanning from single-date search.
All names follow a consistent verb_noun snake_case pattern (find_cheapest_dates, compare_airports, search_flights, find_airport). Verbs accurately reflect each action and no convention mixing is present.
Four tools is well within the sensible 3-15 range and each tool earns its place by covering a distinct query style. Nothing feels redundant or bloated for a flight-search server.
The surface covers single-date search, flexible-date scanning, multi-airport comparison, and code lookup, forming a coherent search workflow. Minor gaps exist for auxiliary parameters like passenger counts, cabin class, or nonstop-only filters, but agents can work around them.