Flight Booking MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USE_REAL_API | No | Set to 'true' to use real flight API backend (Amadeus) instead of mock data. | false |
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_flightsD | – |
| book_flightD | – |
| get_booking_statusD | – |
| cancel_bookingD | – |
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: searching, booking, canceling, and checking status. No overlap.
All tools follow a consistent verb_noun pattern (e.g., search_flights, book_flight).
4 tools is appropriate for a flight booking server, covering core operations without being over- or under-scoped.
Covers essential operations (search, book, cancel, status). Missing update booking or other advanced features, but fine for basic usage.