AENA Flights MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AENA_CLIENT_ID | No | Client ID for AENA REST API. Has a working default. | |
| AENA_TENANT_ID | No | Tenant ID for AENA REST API. Has a working default. | |
| AENA_CLIENT_SECRET | No | Client secret for AENA REST API. If not set, the server runs in website-only mode. |
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 |
|---|---|
| search_flightsA | List flights for an AENA airport (arrivals or departures). Codeshares of the same physical flight are collapsed into one entry by default. Filter by flight number and/or a local-time window (e.g. afternoon = fromLocal 12:00, toLocal 20:00). Times in the output are local Madrid time. |
| get_flightA | Find one flight by number at an airport. Convenience wrapper over search_flights that returns the single best match. |
| list_airportsA | List all Spanish airports in the AENA network with IATA/ICAO codes and city. Fetched live, so always current. |
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 3 tools
Each tool has a distinct purpose: search_flights returns a list, get_flight returns a single flight, and list_airports provides airport data. While get_flight is a convenience wrapper over search_flights, the intent is clear and the usage patterns are unambiguous.
All tool names use verb_noun snake_case: search_flights, get_flight, list_airports. The verbs vary (search, get, list) but the pattern is consistent and the naming is predictable.
With only 3 tools, the server is tightly focused on flight and airport information. This is a well-scoped count for the domain—neither too sparse nor overloaded, and each tool serves a clear function.
The domain is read-only flight lookup and airport listing. The set covers listing all airports, searching flights with flexible filters, and retrieving a specific flight. There are no obvious dead ends or missing core operations for this purpose.