amadeus-mcp-server

Created By
BogdanDubenetsa year ago
Overview

what is amadeus-mcp-server?

The amadeus-mcp-server is a server application designed to facilitate the management and processing of data related to the Amadeus platform.

how to use amadeus-mcp-server?

To use the amadeus-mcp-server, clone the repository from GitHub, install the necessary dependencies, and run the server using the provided commands in the documentation.

key features of amadeus-mcp-server?

  • Integration with the Amadeus API for data retrieval.
  • Support for TypeScript, ensuring type safety and better development experience.
  • Easy setup and configuration for developers.

use cases of amadeus-mcp-server?

  1. Managing travel-related data for applications.
  2. Building custom solutions that require integration with Amadeus services.
  3. Facilitating data processing tasks for travel agencies.

FAQ from amadeus-mcp-server?

  • What programming language is used in amadeus-mcp-server?

The server is built using TypeScript.

  • Is there any documentation available?

Yes, documentation is provided in the GitHub repository.

  • Can I contribute to the project?

Yes, contributions are welcome! Please check the contribution guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BogdanDubenets
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago