Amadeus Hotel API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMADEUS_API_KEY | Yes | Your Amadeus API key | |
| AMADEUS_API_SECRET | Yes | Your Amadeus API secret |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| amadeus_hotel_listA | Search for hotels in a specific city. Retrieves a list of hotels based on location and optional filters including amenities, star rating, and hotel name. This is useful for getting an overview of accommodation options in a destination. Always use valid IATA 3-letter city codes (e.g., 'PAR' for Paris, 'NYC' for New York, 'LON' for London, 'SFO' for San Francisco, 'LAX' for Los Angeles). Examples:
|
| amadeus_hotel_searchA | Search for hotel offers (available rooms with pricing) based on location, dates, guests, and other criteria. This tool provides detailed pricing and availability information for specific stay dates, including room types, board options, and cancellation policies. Always use valid IATA 3-letter city codes (e.g., 'PAR' for Paris, 'NYC' for New York, 'LON' for London, 'SFO' for San Francisco, 'LAX' for Los Angeles). Examples:
|
| amadeus_hotel_offerA | Get detailed information about a specific hotel offer using its ID. This provides comprehensive details about an offer that was found in a previous search result, including updated availability and pricing. |
| amadeus_hotel_bookingA | Book a hotel offer for specified guests. This tool allows you to make an actual reservation using an offer ID from a previous search. You'll need to provide guest details and payment information. |
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 clear, distinct purpose: listing hotels, searching offers, getting offer details, and booking. There is no overlap between their functionalities.
All tools share the 'amadeus_hotel_' prefix and follow a verb/noun pattern, but 'offer' and 'booking' are nouns whereas 'list' and 'search' are verbs, causing slight inconsistency.
With 4 tools, the server covers the essential booking flow but is on the lower side. It is reasonable for a focused API but could benefit from a few more tools.
The set covers listing, searching, detailing, and booking hotels, but lacks essential post-booking operations like cancellation or modification, leaving notable gaps.