Google Flights MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERPAPI_API_KEY | Yes | Your SerpAPI API key |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_flightsA | Search Google Flights (via SerpAPI) between two airports. Args:
departure_id: Origin IATA airport code, e.g. "SEA". Multiple origins may
be comma-separated, e.g. "SEA,PDX".
arrival_id: Destination IATA airport code, e.g. "NRT".
outbound_date: Departure date as YYYY-MM-DD.
return_date: Return date as YYYY-MM-DD. Required when trip_type is
"round_trip"; ignored for "one_way".
trip_type: "round_trip" (default) or "one_way".
travel_class: Cabin class.
adults, children, infants_in_seat, infants_on_lap: Passenger counts.
stops: Filter by number of stops.
max_price: Maximum total price in For a round trip, each option's |
| search_multi_cityA | Search a multi-city Google Flights itinerary (2+ separate legs). Args: legs: Ordered list of leg objects, each with "departure_id", "arrival_id", and "date" (YYYY-MM-DD). For example: [{"departure_id": "SEA", "arrival_id": "NRT", "date": "2026-10-03"}, {"departure_id": "NRT", "arrival_id": "ICN", "date": "2026-10-10"}, {"departure_id": "ICN", "arrival_id": "SEA", "date": "2026-10-17"}] travel_class, adults, children, infants_in_seat, infants_on_lap, stops, max_price, currency, max_results, deep_search: as in search_flights. Each option's |
| get_return_flightsA | List the next set of options after selecting a flight. Pass a |
| get_booking_optionsA | List where to book a selected flight and the price at each provider. Pass a |
| track_priceA | Start tracking the price of a route over time. Saves the search as a watch and records its current lowest price. Re-check
with check_prices (or the scheduled checker) to log price history and get
alerted on drops. Set |
| list_price_watchesA | List all saved price watches with their most recent recorded price. |
| untrack_priceA | Delete a price watch (and its recorded history) by id. |
| check_pricesA | Re-check every price watch now, record the prices, and report any drops or target hits. Uses one SerpAPI search per watch. |
| get_price_historyB | Return the recorded price history (timestamp, price) for a watch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pisanuw/claude-google-flights-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server