4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Travelport MCP Server

Bring Flight Booking
to CrewAI

Learn how to connect Travelport to CrewAI and start using 21 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add Offer To WorkbenchAdd Traveler To WorkbenchAuthorize CardCheck Hotel AvailabilityCommit WorkbenchCreate Hotel ReservationCreate WorkbenchGet Hotel RulesPrice Offer FullPrice Offer ReferenceRetrieve Flight ReservationRetrieve Hotel ReservationReverse AuthorizationSearch Flight SpecificSearch FlightsSearch Next LegSearch Stays By IdSearch Stays By LocationSearch Stays CompleteValidate CardVerify Address

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Travelport

What is the Travelport MCP Server?

Connect to Travelport, the world's leading travel commerce platform, and empower your AI agent to handle complex travel itineraries, real-time flight searches, and hotel bookings.

What you can do

  • Flight Intelligence — Search for catalog product offerings, price specific flight legs, and retrieve full pricing details for air offers.
  • Hotel Management — Search for stays by location or ID, check real-time availability, and retrieve detailed hotel rules and policies.
  • Booking Workbench — Initialize reservation sessions (workbench), add offers and travelers, and commit bookings to create official PNRs.
  • Payment & Security — Validate credit cards, verify addresses, and manage payment authorizations directly within the booking flow.
  • Reservation Retrieval — Fetch existing flight and hotel reservations to provide status updates or itinerary details.

How it works

  1. Subscribe to this server
  2. Enter your Travelport credentials (Client ID, Secret, Username, Password, and Access Group)
  3. Start searching and booking travel from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Travel Agents & Concierges — Automate the search and booking process for clients using natural language.
  • Corporate Travel Managers — Quickly retrieve reservation details and check flight availability without manual GDS entry.
  • Developers — Integrate travel booking capabilities into custom AI workflows and travel assistants.

Built-in capabilities (21)

add_offer_to_workbench

Add an air offer to an existing workbench

add_traveler_to_workbench

Add a traveler to an existing workbench

authorize_card

Authorize a payment card

check_hotel_availability

Check hotel availability (v11)

commit_workbench

Commit a reservation workbench to create a booking

create_hotel_reservation

Create a hotel reservation (v11)

create_workbench

Create a new reservation workbench session

get_hotel_rules

Get hotel rules (v11)

price_offer_full

Price an air offer fully from products

price_offer_reference

Price an air offer from a catalog reference

retrieve_flight_reservation

Retrieve an existing flight reservation

retrieve_hotel_reservation

Retrieve an existing hotel reservation

reverse_authorization

Reverse a payment card authorization

search_flight_specific

Perform a flight specific search

search_flights

Search for flight catalog product offerings

search_next_leg

Search for the next leg of a flight itinerary

search_stays_by_id

Search for hotel properties by ID (v11)

search_stays_by_location

Search for hotel properties by location (v11)

search_stays_complete

Perform a complete hotel search (v12)

validate_card

Validate a payment card

verify_address

Verify a payment card address (AAVS)

Why CrewAI?

When paired with CrewAI, Travelport becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Travelport tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Travelport in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Travelport and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Travelport to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Travelport in CrewAI

The Travelport MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 21 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Travelport
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Travelport for CrewAI

Every tool call from CrewAI to the Travelport MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I start a new booking process for a flight or hotel?

You must first use the create_workbench tool to initialize a temporary session. This session allows you to add offers and traveler details before finalizing the booking with commit_workbench.

02

Can I search for hotels in a specific city or near a landmark?

Yes! Use the search_stays_by_location tool. You can provide geographic coordinates or location criteria to find available accommodations in that area.

03

Is it possible to verify a customer's credit card before committing a reservation?

Absolutely. The server includes validate_card and authorize_card tools to ensure payment methods are valid and authorized before you proceed with the commit_workbench action.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →