AirTrail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRTRAIL_API_KEY | Yes | Your AirTrail API key | |
| AIRTRAIL_USER_ID | Yes | Your AirTrail user ID | |
| AIRTRAIL_BASE_URL | No | Base URL of your AirTrail instance (default: http://localhost:5173/api) | http://localhost:5173/api |
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 |
|---|---|
| list_flightsB | List all flights from Airtrail |
| get_flight_itineraryC | Retrieve flight itinerary information including departure and arrival ICAO airport codes for a specific flight number. Returns airport codes in ICAO format. |
| add_flightD | – |
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
The three tools have distinct purposes (add, retrieve specific, list all), but add_flight lacks a description which slightly increases ambiguity.
All tool names follow a consistent snake_case verb_noun pattern, making them predictable.
Three tools is slightly sparse but appropriate for a basic flight tracking server covering add, get, and list operations.
The set covers adding, retrieving, and listing flights, but lacks update and delete operations, which are notable gaps for a complete lifecycle.