flight-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AVIATIONSTACK_API_KEY | Yes | Your AviationStack API key. Get one for free at https://aviationstack.com/signup/free. |
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 current/live flights, optionally filtered by route, airline, or status. IMPORTANT: this returns CURRENT and near-term real-time flights only — it cannot search a future travel date (e.g. "flights on Sept 20th") or historical flights, and it does not include prices. For a specific flight's status, use get_flight_status instead. Args: origin: Optional 3-letter IATA departure airport code (e.g. "JFK"). destination: Optional 3-letter IATA arrival airport code (e.g. "LHR"). airline_name: Optional airline name to filter by (e.g. "American Airlines"). flight_status: Optional status filter: scheduled, active, landed, cancelled, incident, or diverted. max_results: Max number of results to return (1-100, default 10). Provide at least one filter (origin, destination, or airline_name) — an unfiltered call returns an arbitrary global sample and burns quota fast. |
| get_flight_statusA | Get the real-time status of a specific flight by its IATA flight code. Args: flight_iata: IATA flight code, e.g. "AA100" (airline code + flight number). Returns current status (scheduled/active/landed/cancelled/etc.), gate, terminal, delay, and live position if airborne. |
| resolve_airportA | Look up IATA airport codes by city or airport name. Args: keyword: City or airport name, or exact IATA code (e.g. "London", "Heathrow", "JFK"). Minimum 2 characters. max_results: Max number of matches to return (1-20, default 10). Use this before search_flights if you only have a city/airport name rather than a 3-letter IATA code. |
| resolve_airlineA | Look up airline IATA codes by airline name. Args: keyword: Airline name or partial name (e.g. "American", "Emirates"), or exact IATA code (e.g. "AA"). Minimum 2 characters. max_results: Max number of matches to return (1-20, default 10). |
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 purpose: get_flight_status for a specific flight, search_flights for multi-flight search, resolve_airport for IATA code lookup by city/airport name, and resolve_airline for airline code lookup. No overlap or ambiguity.
All tool names follow a consistent snake_case verb_noun pattern: get_flight_status, search_flights, resolve_airport, resolve_airline. No mixing of styles or conventions.
With 4 tools, the server is well-scoped for a flight search MCP: two lookups (airport/airline codes) and two flight operations (search and specific status). Each tool earns its place without being too few or too many.
The tool surface covers the core domain: resolving identifiers, searching live flights, and retrieving detailed status. Gaps like historical or future scheduled flights are explicitly out of scope, so no missing functionality for its stated real-time purpose.