Cruise Itinerary

com.cruise-itineraryv1.0.0Updated Oct 4, 2026

Cruise sailings, itineraries, weekly fare history, port capacity and the Cruise Price Index.

VerifiedStreamable HTTPWeb executableData & AnalyticsLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant look up cruise sailings, day-by-day itineraries, weekly fare history, port capacity and the Cruise Price Index from real data.

What it does
A read-only remote MCP server for cruise data. Tools resolve port, ship and cruise line names to ids, search upcoming sailings by ship, line, port, region, dates, length and fare, return a sailing's dated day-by-day itinerary or a cruise's stop list, show every weekly fare snapshot of one sailing, report monthly ship-days, distinct ships and berths at a port, and return the weekly Cruise Price Index. Each tool returns the same JSON as the matching REST endpoint.
When to use it
Use it when someone wants to research cruises: which sailings call at a given port, what a ship's itinerary looks like day by day, how a fare has moved week by week, how much capacity reaches a port, or how fares are trending overall.
Requirements
A remote endpoint at cruise-itinerary.com/mcp; nothing runs locally. An account is required for every request, including initialize: sign-in is by email link through MCP OAuth 2.1 with PKCE, or clients without OAuth can send an API key from the dashboard in an Authorization Bearer header. A free account includes 500 calls a month; some tools need a Developer or Business plan.
Before you install
Every successful tool call counts as one API call against your plan, and tools above your plan return a message and a pricing link. Tool names and arguments (port, ship or line names, dates, ids) are sent to cruise-itinerary.com with your access token for answering, plan counting and rate limiting. Keep an API key out of shared files. Fares are weekly Monday snapshots, not live or bookable prices; null fares do not say whether a cabin was unoffered or sold out, estimated itinerary days can be…

Installation

In SourceWeft

  1. Open Cruise Itinerary in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

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

README

Cruise Itinerary for Claude, ChatGPT and other MCP clients

[Cruise Itinerary]

Ask an AI assistant about cruises and get answers from real data: which sailings call at a port, what a ship's itinerary looks like day by day, how a sailing's fare has moved week by week, how much ship capacity reaches a port each month, and how cruise prices are trending overall.

This repository holds:

  • the connection details for the Cruise Itinerary remote MCP server at https://cruise-itinerary.com/mcp,
  • a Claude plugin that adds that server plus a cruise-research skill, which teaches Claude the data's caveats,
  • server.json, the server's entry for the official MCP Registry.

The server is run by Cruise Itinerary (Agile Travel Group, Inc., operated as Cruiseable). The data is the same as its REST API: API docs, MCP docs.

What you can ask

  • "Which sailings call at Juneau in July 2027, cheapest balcony first?"
  • "Show me the day-by-day itinerary of that sailing."
  • "Has the fare on this sailing gone up or down since September?"
  • "How many berths of ship capacity reach Cozumel each month next winter?"
  • "What does the Cruise Price Index say about fares this month?"

Tools

All tools are read-only (readOnlyHint: true). Each returns the same JSON as the matching REST endpoint, as structuredContent with an outputSchema.

ToolWhat it answersMinimum plan
resolve_entityA port, ship or cruise line name, however spelt, to the id the other tools takeFree
cruise_price_indexThe weekly Cruise Price Index: latest 12 weeks (Free), or a full series by line, cabin and segment (Business)Free / Business
search_sailingsUpcoming sailings by ship, line, port, departure port, region, dates, length and fare, with the latest weekly faresDeveloper
get_itineraryA sailing's dated day-by-day itinerary, or a cruise's stop listDeveloper
get_price_historyEvery weekly fare snapshot of one sailingBusiness
port_month_capacityShip-days, distinct ships and berths at one port, month by monthBusiness

A free account (an email address, no card) includes 500 calls a month. Every successful tool call counts as one API call. A tool above your plan answers with a short message and a link to pricing.

Setup

Claude (claude.ai, Desktop, mobile)

Add it as a connector: Customize → Connectors → Add custom connector, name it Cruise Itinerary, and paste https://cruise-itinerary.com/mcp. Claude detects the OAuth sign-in and asks you to sign in when you add it: enter your email, open the link we send, then approve the connection.

To get the cruise-research skill as well, install this repository as a plugin (below) or from the Claude directory once it is listed.

Claude Code

As a plugin (server and skill):

/plugin marketplace add BigBalli/cruise-itinerary-mcp/plugin install cruise-itinerary@cruise-itinerary

Or the server only:

claude mcp add --transport http cruise-itinerary https://cruise-itinerary.com/mcp

Then run /mcp and choose cruise-itinerary to sign in.

ChatGPT

Add a custom app (connector) with the URL https://cruise-itinerary.com/mcp and OAuth authentication. Until the listing appears in the ChatGPT directory, this needs developer mode.

Cursor, VS Code, Windsurf and other clients

Point the client at the URL. Clients that support MCP OAuth sign in in the browser:

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

Clients without OAuth can send an API key from your dashboard as a header instead. Keep the key out of shared files.

json
{  "mcpServers": {    "cruise-itinerary": {      "url": "https://cruise-itinerary.com/mcp",      "headers": { "Authorization": "Bearer <your API key>" }    }  }}

How sign-in works

The server follows the MCP authorization specification: OAuth 2.1 with PKCE (S256), protected resource metadata at https://cruise-itinerary.com/.well-known/oauth-protected-resource/mcp, and an authorization server at https://cruise-itinerary.com that supports Client ID Metadata Documents and dynamic client registration. Sign-in is by email link; a new address gets a free account. You approve each app on a consent page that shows which app is asking and where it returns you. Access tokens last an hour and refresh tokens rotate on use. Connecting never shares your API keys, email address or billing with the app, and the app can only read.

Every request needs an account, initialize included: without a token the server answers 401 with a WWW-Authenticate header pointing at the protected resource metadata, which is how clients know to start sign-in.

Read the data the right way

  • Fares are weekly snapshots captured every Monday since 6 September 2026, not live or bookable prices. meta.as_of gives the load date.
  • A missing (null) fare means the cabin was not offered or was sold out; the data does not say which.
  • Itinerary days marked estimated were placed from the distance between ports and can be off by a day. exact days come from the cruise line's published itinerary.
  • Port capacity is monthly only, and berths are ship capacity, not passengers.
  • Coverage is strongest for North American cruise lines. TUI Cruises/Marella, AIDA, Saga, Fred. Olsen and Hapag-Lloyd are not covered.

Data and privacy

The plugin contains no code that runs on your machine. It declares one remote MCP server, https://cruise-itinerary.com/mcp, and one skill made of instructions. When your assistant calls a tool, the tool name and its arguments (names of ports, ships or lines, dates, ids) go to cruise-itinerary.com with your access token. They are used to answer the call, count it toward your plan and enforce rate limits. Nothing else is sent, and nothing is sent anywhere else.

License

MIT, see LICENSE. The data served by the API is covered by the Cruise Itinerary terms, not by this license.

Source: README.md at commit fb8c844

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 4, 2026