The Flight MCP Server provides real-time flight data by integrating with the Amadeus API and exposes several tools through the Model Context Protocol (MCP) so Claude Desktop can perform flight searches, retrieve airport and airline information, and check flight statuses. The server is implemented in Python and runs as a modular MCP service, handling authentication, data validation, and graceful fallbacks to mock data if the Amadeus API is unavailable. You can interact with the server through Claude Desktop by invoking tools such as search_flights, get_airport_info, get_flight_status, and get_airline_info to obtain structured flight information in natural language queries.

To use the server, start it with the provided command, ensure your Amadeus credentials are set in the environment, and configure Claude Desktop to point at the server via the integration configuration. Once running, you can ask Claude things like: "Search for flights from LAX to JFK tomorrow", "What’s the status of flight AA123 today?", or "Tell me about San Francisco airport". Each tool returns data appropriate for conversational use, including flight options, airport details, statuses, and airline information.

Prerequisites:

• Python 3.10+
• Access to Amadeus API credentials (API key and secret)
• git

Install steps:

1. Clone the repository: git clone https://github.com/technicalerikchan/flight-mcp-server.git
2. Change directory: cd flight-mcp-server
3. Create and activate a virtual environment (recommended): python -m venv venv

   Windows

   venv\Scripts\activate.bat

   macOS/Linux

   source venv/bin/activate
4. Install dependencies: pip install -r requirements.txt
5. Copy the environment template and supply credentials: cp .env.example .env

   Edit .env and add your credentials

6. Run the server: python -m flight_mcp_server.server

Notes:

• Ensure the Amadeus credentials in the environment file are correct and have the necessary permissions.
• If the API is unavailable, the server will automatically fall back to mock data.

Environment and configuration tips:

• Keep your Amadeus API credentials secure; do not commit them to source control.
• If you encounter authentication issues, verify the values in the .env file and check for accidental whitespace.
• The server includes a smart fallback to mock data when the Amadeus API is unreachable to maintain responsiveness.
• You can customize environment variables or add additional configuration as needed; ensure the MCP server stays in sync with Claude Desktop configurations.
• Typical issues include network connectivity problems or API rate limits; in such cases, mock data will be used to maintain functionality.