A travel booking MCP server
for AI agents.

If you are comparing travel-related MCP servers, three questions decide most of it: where the supply comes from, who controls what an agent may do, and whether a booking is real. Here, the supply is what an agency or tour operator manages in the Adrasis Console. That inventory owner controls access through a partner account and its scopes. A successful book call creates the reservation and reduces inventory, exactly as a REST booking does.

Nothing is reinterpreted for agents. Tools use the same request and response schemas, business logic, pricing and usage rules as the REST contract, so an agent and a conventional integration work from one set of rules.

# Remote MCP server, streamable HTTP
https://ari.console.adrasis.com/mcp

# OAuth 2.0 access token
Authorization: Bearer <access token>

An agent can also skip MCP and call the REST contract directly. The full machine-readable contract is published in the API reference.

Accommodation

Reference data, property content, availability search and the full booking lifecycle for hotels, vacation rentals, villas and apartments.

The single-property offer search, which lists up to twenty choices for one property, is available through REST only.

Transfer, tour and flight

Each product follows the same search, prebook and book pattern as accommodation. Flights are charter flights, and a round trip is searched as two separate legs.

Packages

A package sells 2 to 5 services the agent has already selected, across at least two product types, at one inclusive price. Either every service confirms or none does. Once booked, a package is read and canceled with get_booking, cancellation_quote and cancel, and the last two can also target single services inside it.

Trip grouping

A trip groups bookings that are already confirmed into one itinerary. Each booking keeps its own total, cancellation policy and lifecycle, so a trip is never a priced package.

The partner exchanges its client ID and client secret for an access token at https://ari.console.adrasis.com/api/v1/oauth/token. The token is valid for one hour, and no refresh token is issued: when it expires, the agent requests a new one with the same credentials. The documentation recommends keeping one token and renewing it shortly before it expires, rather than requesting one per call.

The token travels in the Authorization header of the MCP session. The partner account and the token's scopes are forwarded unchanged on every tool call, and a call to a tool whose scope the token lacks is rejected.

Two scopes

Grant only what the agent needs. An agent that answers availability questions but must never book gets distribution:read alone. New credentials receive both scopes by default, so pick the minimum when you create one for an agent. A token can also be requested with a narrower scope than its credential holds. Error codes and the remaining details are in the authentication guide.

1. Partner account

   The owner opens Partner Network, then Partner Accounts, and creates one account for the relationship. A Default profile comes with it.

2. Channel Portfolio

   The owner opens the intended properties in each profile: one at a time, as a group, or from country and place filters.

3. Credentials

   A separately named credential for each environment, with the minimum scopes. The secret is shown once, so it goes straight into a secret manager.

4. Certification and go-live

   Pilot credentials see a demonstration catalog. On promotion to live supply, the client ID, host and integration flow stay the same.

The demonstration catalog has rates and availability generated for testing, and test bookings neither affect real allotment nor create charges. Cancel every test booking anyway: an open test booking holds demonstration allotment, and repeated tests can start returning SOLD_OUT.

No fixed request ceiling is published. Request limits are agreed for each connection, so confirm them with your Adrasis contact before raising traffic. Adding credentials or profiles does not add allowance. The owner can rotate, disable or revoke a credential from the account's API Access tab, and a disabled or revoked credential stops working together with the tokens minted from it.

The owner's side is described in Partner Network and API credentials. If your team is building a travel agent and wants to become a partner, contact us.