Cruise Itinerary

What Cruise Itinerary MCP server does

The Cruise Itinerary MCP server exposes read-only cruise data through a remote MCP endpoint at https://cruise-itinerary.com/mcp. It is intended for questions about cruise schedules, ports, ships, fares, capacity, and broader price trends. The returned data matches the service's REST API and is provided as structured content with an output schema.

The service can identify ports, ships, and cruise lines even when a name is spelled differently. It can then use those identifiers to search upcoming sailings, inspect a sailing's stops, review historical fare snapshots, or measure monthly capacity at a port.

How it works

Clients connect to the remote endpoint over HTTP. OAuth 2.1 with PKCE is supported for clients that can complete browser-based sign-in. Authentication uses an email link, and a new email address receives a free account. Clients without OAuth support can send an API key in the Authorization header.

Each request, including initialize, requires an account token. Access tokens last one hour, while refresh tokens rotate when used. The server does not modify cruise data: every listed tool is read-only. Successful calls count against the account's API allowance, and tools outside the account's plan return a short explanation with pricing information.

Setup and configuration

For Claude, add https://cruise-itinerary.com/mcp as a custom connector and complete the browser sign-in flow. Claude Code can add the remote server with its HTTP MCP command, or install the repository's plugin to receive the server and the cruise-research skill.

Other compatible clients can use a remote-server configuration such as:

{
  "mcpServers": {
    "cruise-itinerary": {
      "url": "https://cruise-itinerary.com/mcp"
    }
  }
}

For a client without OAuth, replace the configuration with an Authorization: Bearer <your API key> header. Keep API keys out of shared configuration files. The repository's plugin contains connection metadata and instructions; it does not run application code locally.

Tools and capabilities

The Cruise Itinerary MCP server provides six tools:

• resolve_entity maps a port, ship, or cruise line name to an identifier.
• search_sailings filters upcoming cruises by ship, line, ports, region, dates, duration, and fare, and includes recent weekly fares.
• get_itinerary returns dated daily stops for a sailing or a cruise stop list.
• get_price_history returns weekly fare snapshots for one sailing.
• port_month_capacity reports monthly ship-days, distinct ships, and berth capacity at a port.
• cruise_price_index returns the latest 12 weeks for free access, with broader breakdowns by line, cabin, and segment on Business access.

Limitations and notes

Cruise fares are weekly snapshots captured on Mondays, not live or bookable prices. The meta.as_of field identifies the load date. A null fare means the cabin was unavailable or sold out, without distinguishing between those causes.

Itinerary days marked estimated are inferred from port distances and may be off by a day; exact days come from a cruise line's published itinerary. Capacity data is monthly, and berth figures represent ship capacity rather than passenger counts.

Coverage is strongest for North American cruise lines. TUI Cruises/Marella, AIDA, Saga, Fred. Olsen, and Hapag-Lloyd are not covered. A free account includes 500 calls per month, while some tools have plan-specific access or a 10-call monthly trial. The data is governed by the service's terms rather than the repository's MIT license.