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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_search_flightsA | Search for flights on a specific route and date. Args: departure: Departure airport IATA code (e.g. MAD, BER, MUC) arrival: Arrival airport IATA code (e.g. BER, MAD, LHR) date: Departure date in YYYY-MM-DD format return_date: Optional return date in YYYY-MM-DD format (omit for one-way) passengers: Number of adult passengers (default 1) stops: Stop filter — 1=nonstop only, 2=1 stop max, 3=2 stops max (default: any) travel_class: 1=economy, 2=premium economy, 3=business, 4=first (default 1) sort_by: Sort order — 1=top flights, 2=price, 3=departure time, 4=arrival time, 5=duration currency: Price currency ISO code (default EUR) max_price: Maximum price filter in the specified currency Returns: JSON with best_flights, other_flights arrays, and Google Flights URL |
| mcp_get_booking_optionsA | Get booking links and prices for a specific flight. Use the booking_token from a search result to get actual booking URLs from airlines and travel agencies. Args: booking_token: The booking_token from a flight in search results currency: Price currency ISO code (default EUR) Returns: JSON with booking_options array containing provider, price, and booking URL |
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 2 tools
The two tools have clearly distinct purposes: one searches for flights, the other retrieves booking options for a selected flight. There is no overlap or ambiguity.
Both tool names follow the same verb_noun pattern with the mcp_ prefix: mcp_search_flights and mcp_get_booking_options. This is consistent and predictable.
With only two tools, the server feels thin for a full flight search domain. It is borderline, as the two tools cover the core search-then-book flow, but the count is at the low end of acceptable.
The tool set covers the essential flight search and booking link retrieval process. Minor gaps exist, such as lacking airport code lookup or multi-city search, but the primary workflow is complete for standard one-way/round-trip searches.