Amadeus Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

MCP server for Amadeus travel: flights, hotels, airports. Free test key.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Local MCP server that connects an assistant to Amadeus travel data for flights, hotels and airports.

What you can do
  • Look up flights, hotels and airports through the Amadeus travel APIs.
  • The registry description names these three areas but does not list individual tools, so exact operations are not documented here.
  • Runs as a local stdio process started by the assistant.
When to use it
Useful when you want an assistant to help with travel research — finding flights, checking hotels or looking up airport information — inside a chat session rather than a booking site.
Requirements
Runs as a local process, installed from the npm package amadeus-mcp over stdio. The manifest declares no authentication, environment variables or headers, but the description mentions a free test key, so an Amadeus API key is likely needed; confirm the setup before installing. Desktop client only.
Before you install
The description mentions a free test key, which suggests an Amadeus API credential must be supplied; keep it private and check whether the free tier has usage limits or later billing. No tool list is published, so what the server can read or change is unverified. Travel data is sent to Amadeus as a third party.

Installation

In SourceWeft

  1. Open Amadeus Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.1LatestOct 17, 2026
  2. v1.0.0Sep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.