Get the FREE Ultimate OpenClaw Setup Guide →

amadeus -standalone

MCP server from privilegemendes/amadeus-mcp-server-standalone

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio privilegemendes-amadeus-mcp-server-standalone node path/to/server.js \
  --env AMADEUS_CLIENT_ID="your_client_id" \
  --env AMADEUS_CLIENT_SECRET="your_client_secret"

How to use

This MCP server provides travel-focused capabilities by interfacing with the Amadeus API. It exposes tools to search for flights, look up airports, analyze price trends, determine the cheapest travel dates, and retrieve detailed flight information. You can leverage prompts like analyze-flight-prices to gauge pricing dynamics for a route, find-best-deals to identify top flight offers for a given route and date, plan-multi-city-trip to optimize routing across multiple destinations, and find-cheapest-travel-dates to surface economical travel windows. To use the server, connect your AI assistant or client to the server endpoint and invoke these tools as needed. Each tool accepts parameters such as origin/destination airports, travel dates, passenger counts, and filters (e.g., cabin class, nonstop only).

How to install

Prerequisites:

  • Node.js 16.x or higher
  • npm (comes with Node.js)
  • Amadeus API credentials (Client ID and Client Secret)
  1. Clone the repository:
git clone https://github.com/yourusername/amadeus-mcp-server.git
cd amadeus-mcp-server
  1. Install dependencies:
npm install
  1. Create a .env file in the root directory with your Amadeus API credentials:
AMADEUS_CLIENT_ID=your_client_id
AMADEUS_CLIENT_SECRET=your_client_secret
  1. Build (if a build step exists) and run the server:
npm run build
npm start

For development:

npm run dev

Additional notes

Environment variables and configuration:

  • AMADEUS_CLIENT_ID and AMADEUS_CLIENT_SECRET are required for authenticating with the Amadeus API.
  • Ensure these credentials are kept private and loaded from the environment (.env or hosting secret manager).
  • If you encounter rate limiting from Amadeus, implement retry/backoff in your client or enable any provided API rate-limit handling.
  • Tests may require actual Amadeus credentials in a test environment; for CI, consider using mocks where available.

Common issues:

  • Missing credentials causing authentication errors: verify .env values are loaded.
  • Network or DNS issues: ensure server can reach Amadeus endpoints.
  • Node version compatibility: confirm Node.js version matches the server's requirements.

Related MCP Servers

Sponsor this space

Reach thousands of developers