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. Options: 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
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 distinct role: initiating search, retrieving filtered results, getting detailed info on a specific option, and requesting a booking link. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (search_flights, get_flight_options, get_flight_option_details, request_booking_link), making them predictable and easy to use.
With 4 tools, the surface is well-scoped for a flight search and booking workflow—lean yet covering essential steps without redundancy.
The tools cover the core flight search workflow: initiate search, filter results, view details, and obtain a booking link. Minor gaps (e.g., no tool for managing bookings) are acceptable given the server's focused purpose.