Google Flights Fares MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | An Apify API token from https://apify.com/account/integrations. Required to call the tool (the server can list its tool without a token, but a tool call needs one). |
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 |
|---|---|
| get_google_flights_faresA | Search Google Flights for a route and dates. Returns one row per flight option with price, airlines, flight numbers, departure and arrival times, duration, stops, layovers, and emissions. |
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
Only one tool exists, so there is nothing to confuse it with. Its purpose—searching Google Flights for a route and dates—is crystal clear from the name and description.
A single descriptive snake_case verb_noun name (get_google_flights_fares) with no competing conventions to clash with. It is readable and self-explanatory.
One tool is thin even for a narrowly scoped fare-search server; there is no way to resolve airport codes, propose flexible dates, or fetch details. The single tool does earn its place, but the surface is minimal.
The core search flow is covered, but the surface is a dead end: no filters (cabin class, max stops, passengers), no date-flexibility option, and no way to retrieve a specific fare's details or booking link. Agents can work around this only by re-calling with different arguments.