Developer API

Travel Forecast exposes a free, public API for cruise travel data — curated port destinations with month-by-month climate, regional weather guides, and a live database of upcoming cruise sailings — plus an MCP server that wraps the same reads as tools for AI agents, with one additional tool that can plan a trip in a signed-in user's account behind OAuth.

REST reads: no authJSON responses60 req / min / IPOpenAPI 3.1MCP: OAuth for writes

OpenAPI 3.1 spec AI plugin manifest llms.txt

Attribution

Responses include a canonical url for each item. If you surface this data, please link back to the source page on travel-forecast.com. Editorial text is licensed CC BY 4.0 (link-back required). The live 15-day forecast is not part of this API. It renders only on the site.

MCP Server

The same data is also available as a Model Context Protocol server at https://travel-forecast.com/api/mcp (Streamable HTTP, JSON-RPC 2.0) — point an MCP-aware client at that URL and call these tools directly instead of hitting the REST endpoints above. Five tools are read-only and need no authentication, same as the REST API; a sixth, plan_trip, writes to a signed-in user's account and requires a real OAuth 2.1 flow.

Tool	What it does	Auth
list_destinations	List curated cruise ports with slug, region, category, and best-month list.	None
get_destination	Get one port: overview, highlights, month-by-month climate, and a canonical url.	None
list_cruise_guides	List regional cruise weather guides (Caribbean, Alaska, Mediterranean, Bahamas).	None
get_cruise_guide	Get one region: month-by-month weather ratings and a canonical url.	None
search_cruises	Search live upcoming cruise sailings by cruise line, ship, and/or departure date.	None
plan_trip	Create a trip (up to 10 stops) in the signed-in user's account and return its shareable URL. Max 3 active trips per account.	OAuth 2.1

oauth-protected-resource oauth-authorization-server

How plan_trip authorization works

This is a real, spec-conformant OAuth 2.1 authorization server (per the MCP 2025-06-18 authorization requirements) — not a static API key. A conformant MCP client can discover and complete the whole flow on its own, starting from the two documents linked above.

Dynamic client registration — the client self-registers (RFC 7591) and gets back a client_id. No manual setup on either side.
Owner approval — a newly registered client can't complete a token exchange yet; the site owner approves or revokes it from an internal admin panel first. (Clients that authenticate via a Client ID Metadata Document — Claude included, see the walkthrough below — skip this step and are trusted automatically.)
User consent — the signed-in user sees a consent screen and approves the trips:write scope for that specific client.
PKCE token exchange — the client exchanges its authorization code (with an S256 PKCE code verifier, since this server only issues to public clients — no client secret) for a short-lived Bearer access token, sent as Authorization: Bearer <token> on the plan_trip call.

Adding this server to Claude as a custom connector

This server publishes a Client ID Metadata Document, so Claude.ai, Claude Desktop, and the Claude mobile apps can detect it, register themselves, and complete the OAuth handshake automatically — no dynamic-client-registration step and no waiting on the admin approval described above.

In Claude, open Settings → Connectors and click Add custom connector.
For Name, enter anything, e.g. Travel Forecast.
For URL, paste https://travel-forecast.com/api/mcp exactly, then click Add.
Claude should show the authentication setting already on "Required when the server asks" — that's correct, since only plan_trip needs a token and the other five tools don't.
Click Connect, sign in to your Travel Forecast account if prompted, and approve the trips:write consent screen. Claude redirects back and the connector is ready.

If Claude instead shows "None — Detected": its setup probe only calls the five unauthenticated tools and never touches plan_trip, so on an older Claude client (or a non-Claude MCP client without CIMD support) it can wrongly conclude the server needs no auth at all. Open the connector's settings and change the dropdown to "Required when the server asks" by hand — otherwise the first plan_trip call will fail instead of triggering the sign-in flow.

Sea you in a moment

Hang tight. We're checking the weather.