google-flights-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| search_flightsA | Search for one-way or round-trip flights. Returns prices, airlines, durations, stops, aircraft, emissions, and price context (low/typical/high). |
| search_multi_cityB | Search for multi-city (multi-leg) flight itineraries. Supports 2-5 segments. |
| get_price_insightsB | Find the cheapest travel dates for a route within a date range. Scans multiple departure dates. |
| get_calendar_heatmapA | Get a full calendar of daily flight prices (~60 days). Single API call, no scanning. Shows cheapest dates at a glance. |
| compare_cabin_classesA | Compare prices across economy, premium economy, business, and first class for the same route in one call. |
| track_priceA | Track a flight price over time. Records the current cheapest price and reports if it has gone up, down, or stayed stable since last check. |
| get_price_historyA | View the recorded price history for a tracked route. Shows all past observations and the trend. |
| list_tracked_routesA | List all routes currently being price-tracked, with their last known price and number of observations. |
| lookup_airportA | Look up airport IATA codes by city name, airport name, or country. Searches 8,800+ airports. |
| find_nearby_airportsA | Find alternative airports near a given airport within a radius. Useful for finding cheaper flights from nearby cities. |
| get_flight_urlB | Generate a direct Google Flights URL for a route. Users can click to view and book flights in their browser. |
| analyze_layoversA | Analyze layover quality for connecting flights. Reports connection time, risk level (tight/comfortable/long), and aircraft details. |
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 12 tools
Each tool has a distinct primary purpose (search, multi-city, airport lookup, price tracking, URL generation, layover analysis). The only mild overlap is get_price_insights vs get_calendar_heatmap, which both surface cheapest dates, though their descriptions differentiate them by scanning strategy.
All 12 tools use consistent snake_case verb_noun patterns (get_, list_, search_, compare_, track_, lookup_, find_, analyze_). The verb choices map predictably to each tool's action.
12 tools is a well-scoped set for a flight search domain, with each tool earning a distinct place across search, pricing, airport, and analysis concerns.
The surface covers search (one-way/round-trip/multi-city), price tracking lifecycle (track/list/history/insights/calendar), airport discovery, cabin comparison, and URL handoff for booking. Minor gaps remain (e.g. no filter/detail refinement or direct booking), but core workflows have no dead ends.