Connect your AI Agents to Sabre in minutes

What is a Sabre MCP?

It's an MCP server that connects your agents to Sabre's global distribution system via tools. Your agents can invoke these tools to search for flights and hotels, retrieve fare ranges, create bookings, check ticket status, and more.

Sabre offers an official MCP server, but you can also use one from a third-party platform, like Merge Agent Handler.

How can I use the Sabre MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Automated corporate booking: When a traveler submits a trip request via an internal tool, an agent searches for available flights in Sabre, applies company travel policy rules around fare class and preferred airlines, and creates the booking automatically without requiring manual intervention

• Fare monitoring and alerts: An agent queries Sabre's low fare forecast for a set of high-frequency routes, compares results against existing bookings, and sends a Slack message to the travel manager when prices drop below a defined threshold

• Flight and hotel bundling: An agent searches for flights and hotel options in parallel for a given destination and date range, then presents a combined itinerary ranked by total cost and compliance with the company's travel policy

• Conversational travel planning: A corporate travel assistant agent takes a destination and preferred travel window from a chat interface, retrieves fare ranges and available hotel properties from Sabre, and returns a curated set of options for the traveler to review

What are popular tools for Sabre's MCP server?

Here are some of the most commonly used tools:

• search_flights: retrieves available flights for a given origin, destination, date range, and passenger count from Sabre's GDS. Call this at the start of any travel booking workflow to surface current availability and pricing

• create_booking: creates a confirmed reservation in Sabre for a selected flight itinerary with passenger and payment details. Use this when an agent has identified the right fare and is ready to complete the booking

• get_booking: fetches full details of an existing reservation, including flight segments, passenger records, and current status. Helpful when an agent needs to verify itinerary details before modifying, cancelling, or surfacing a trip to a traveler

• search_hotels: searches for available hotel properties in a destination for specified dates and guest count. Call this when an agent needs to present lodging options alongside a flight or handle a hotel-only booking request

• get_low_fare_forecast: returns predicted low fare windows for a route over a future date range. Use this when an agent needs to advise on the best time to book or trigger a price alert for a monitored route

• get_fare_range: retrieves the current minimum and maximum fares available for a given route and date. Good for agents that need to benchmark a specific fare against the broader market before recommending a booking to a traveler

What makes Merge Agent Handler's Sabre MCP server better than alternative Sabre MCP servers?

Here's what sets Merge Agent Handler's Sabre MCP server apart from a custom integration or alternative build:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Sabre, this means you can prevent passenger details, itinerary records, and fare pricing data from being exposed even when the agent has broad access to the GDS

• Managed authentication and credentials: Merge stores and refreshes Sabre credentials on your behalf. You never expose raw API keys or OAuth tokens to an agent or deal with manual token rotation when credentials change

• Real-time observability and audit trail: Every tool call made against Sabre is logged with timestamp, tool name, input parameters, and response metadata. Travel ops and finance teams can audit exactly what an agent searched, booked, or retrieved without writing any logging infrastructure themselves

• Tool Packs and controlled access: Tool Packs let you bundle specific Sabre tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Sabre MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account.

2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.

3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.

4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose Sabre and complete the auth flow. Merge stores and manages the credentials going forward.

5. Open a Claude Code session and start querying Sabre data directly. The first time you use a Sabre tool, a Magic Link may appear to complete connector authentication.

If you want to connect Merge Agent Handler's Sabre MCP with internal or customer-facing agentic products, you can follow the steps in our docs.

Can employees use Merge Agent Handler to connect their AI tools to Sabre?

Yes, Agent Handler for Employees lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, and other MCP-compatible AI tools to Sabre without bypassing IT governance.

Instead of setting up direct connections with personal credentials that IT can't monitor or revoke, each employee authenticates through Agent Handler and gets individual credentials tied to their identity.

IT also provisions access by role or group via SCIM. A travel agent, for example, gets Sabre access to book and manage flight and hotel reservations, Outlook to manage customer communications, and Salesforce to track client accounts and preferences; while a corporate travel manager gets Sabre access to monitor booking activity and policy compliance, Expensify to reconcile travel costs, and Slack to coordinate with the travel team on itinerary changes.

Every tool call an employee's AI makes to Sabre is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.