Flights MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLIGHTS_HTTP_PATH | No | URI path for the endpoint (only used when FLIGHTS_TRANSPORT is streamable_http or sse) | /mcp |
| FLIGHTS_HTTP_PORT | No | Port for HTTP/SSE transport (only used when FLIGHTS_TRANSPORT is streamable_http or sse) | 4200 |
| FLIGHTS_TRANSPORT | No | Transport protocol to use (stdio, streamable_http, sse) | stdio |
| FLIGHTS_AVIASALES_MARKER | Yes | Your Aviasales marker ID | |
| FLIGHTS_AVIASALES_API_TOKEN | Yes | Your Aviasales API token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_flightsA | Search for flights using the Aviasales Flight Search API. This tool performs search based on the provided flight segments, number of passengers, trip class, currency, and locale. It provides search_id and description of search results and saves found options internally.After receiving the result client can use |
| get_flight_optionsA | Get flight options from the previously performed search. This tool allows you to filter the found flight options by price, departure and arrival times, and airlines. It returns a paginated list of flight options that match the specified filters and sorting option.IMPORTANT: This is very cheap operation, so you can call it as many times as needed to find the best flight options. |
| get_flight_option_detailsA | Retrieve detailed information about a specific flight option from the search results. This tool provides detailed information about a flight option, including its segments, price, baggage info. It is useful for getting more granular information about a specific flight option. |
| request_booking_linkA | Request link for booking a flight option. This tool generates a booking link for a specific flight option.This tool is recommended to be used after the user expressed intention to book the flight option. |
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
Each tool has a clearly distinct purpose in the flight booking workflow: search_flights initiates a search, get_flight_options retrieves and filters results, get_flight_option_details provides granular details, and request_booking_link handles final booking. There is no functional overlap between these tools.
All tools follow a consistent verb_noun naming pattern (search_flights, get_flight_options, get_flight_option_details, request_booking_link) with clear, descriptive names that accurately reflect their functions.
Four tools is well-scoped for a flight search and booking server, covering the essential workflow from search to booking without being overly sparse or bloated. Each tool earns its place in the sequence.
The toolset covers the core flight search and booking workflow effectively, but lacks explicit tools for operations like canceling bookings, managing user profiles, or handling payment details, which might be expected in a comprehensive flight booking system.