Goliath docs
Goliath is a free, read-only remote MCP server for travel. One connection gives an assistant or agent reviewed travel sources, award-program and transfer rules, and exact arithmetic for comparing quotes.
- Server URL
https://goliath.travel/mcp- Authorization
- OAuth, approved in your browser. No account, email or API key.
- Cost
- Free, with a daily search allowance per workspace.
- Writes
- None. It never books, pays, transfers points or holds a seat.
Connect
Add a remote MCP server in your assistant with this URL, then approve the connection in the browser window it opens.
https://goliath.travel/mcp
From a terminal
Codex:
codex mcp add goliath --url https://goliath.travel/mcp
codex mcp login goliath
Claude Code:
claude mcp add --transport http --scope user goliath https://goliath.travel/mcp
From a config file
Cursor reads ~/.cursor/mcp.json. Merge this entry and keep your other servers:
{
"mcpServers": {
"goliath": {
"url": "https://goliath.travel/mcp"
}
}
}
In the browser
Browser agents that support WebMCP can call three read-only tools on this site: find_travel_sources, get_source_coverage and get_connection_setup. They list sources, coverage and setup steps; searches run through the MCP server.
Guides for each assistant
Each guide has a setup prompt you can paste into the assistant and the manual steps.
To check the connection, ask your assistant to call get_service_status. The Codex connection has been tested from start to finish; the other guides follow each assistant’s published instructions.
Tools
Goliath exposes five read-only tools and one prompt. Nothing here books, pays, transfers points or holds a seat.
| Tool | What it does | Calls out to |
|---|---|---|
get_service_status | Limits, storage policy and a summary of supplier health | Nothing |
find_sources | The reviewed catalogue, award-program coverage, booking guidance, or MCP Registry candidates | Registry mode only |
get_supplier_tools | One installed supplier’s current tool names and input schemas | That supplier |
search_travel | A planned search from requirements, a flexible award search, or one to four explicit supplier requests | Suppliers |
compare_quotes | Exact arithmetic on quotes the assistant already has | Nothing |
The plan_trip prompt is a full planning walkthrough. A sixth tool, connect_seats_aero, appears only when the operator has registered a Seats.aero app; it links or unlinks the traveler’s own Seats.aero account.
The assistant keeps the planning context. There are no trip, saved-search or result-polling tools.
Searching
search_travel takes exactly one of three inputs:
requirements: travelers, destinations, dates and preferences. The planner runs live-capable sources first and makes at most four supplier requests per call. When more remain it returnsnext_offset; repeat the same requirements with that value asplan_offset.award_search: a flexible award search across dates.searches: one to four explicit requests, each{"supplier_id", "tool", "arguments"}. Read the supplier’s current schema withget_supplier_toolsfirst.
{
"requirements": {
"travelers": [
{ "id": "traveler-1", "origin": "JFK", "age_group": "adult" }
],
"destinations": [{ "name": "London", "airport": "LHR" }],
"departure_date": "2027-03-12",
"return_date": "2027-03-19",
"currency": "USD",
"max_stops": 0,
"rewards": {
"cabin": "economy",
"loyalty_programs": ["virginatlantic"]
}
},
"freshness_policy": "prefer_live"
}
requirementsplans a round trip, soreturn_dateis required. For a one-way fare, send an explicit request insearches.rewards.loyalty_programstakes redemption-program IDs such asaeroplan,flyingblue,unitedandvirginatlantic. If an ID can’t be mapped exactly, award queries are skipped with a warning rather than widened.- Hotel planning needs
lodging.check_in,check_out,adults,children_agesand a two-letterguest_country. Flight departure is never assumed to be the check-in date. max_result_charssets the reply budget: 60,000 by default, from 10,000 to 400,000.result_detail: "offers"drops the raw supplier response wherever normalized offers were built.
Replies and offers
Every tool returns one JSON text block; parse content[0].text. A search_travel reply holds status, results, warnings, planned_requests, omitted_requests, next_offset and result_budget.
Each result names its supplier_id, the native tool, the exact request, and a status of completed, failed or skipped. Failures stay in the reply. For suppliers whose response shape has been reviewed, a result also carries offers in one common shape:
{
"schema": "goliath.offer.v1",
"count": 1,
"recognized_rows": 1,
"items": [{
"kind": "cash_flight", "basis": "itinerary",
"origin": "JFK", "destination": "LIS",
"departure": "2026-11-20T18:05", "return_date": null,
"trip_type": "one_way", "cabin": "economy", "stops": 0, "flights": ["TP202"],
"cash": { "amount": 412, "currency": "USD", "taxes_included": true },
"points": null,
"price_scope": "whole_party", "passengers": 2,
"freshness": "live", "link": "https://...", "link_kind": "search",
"source_pointer": "/flights/0"
}]
}
basisis anitinerary, onecalendar_dayof a fare calendar, or apublished_farecard.- Amounts are exactly as the source reported them: never converted, summed or checked at checkout.
nullmeans the source didn’t state it. linkopens the page where the option is booked or checked, andlink_kindsays which page it is:booking(the seller’s own booking page with the route and date filled in),search(a search page that lists it) orsource(the source’s page about the fare).source_pointerlocates the original row in the supplier response, which is kept alongside the offers.- A reply’s
statusiscompleted,partial,failed,needs_requirements,unavailableorexhausted.completedmeans the calls answered, not that coverage was complete.
Interactive results
In assistants that support MCP Apps, such as Claude and ChatGPT, search_travel also shows its reply as a table: the ui://goliath/search-results.html resource, named in the tool’s _meta.ui.resourceUri. Each option sits on one row with its source and freshness, the rows sort by price, points, duration or departure, and each row’s Book or View button opens its link in the traveler’s browser: Book for a seller’s booking page, View for any other page. The table reads the same JSON reply and adds nothing to it; assistants without MCP Apps get the JSON alone.
Freshness
Every price carries one of three labels.
- Live
- Asked just now, while your assistant waited.
- Cached
- Seen earlier, with its age. Used when a live search isn’t possible.
- Published
- An award chart, transfer table or rules page the program publishes itself.
prefer_live, the default, tries the source first. If that fails with an availability, timeout, rate-limit or response error, an unexpired public snapshot may come back with an explicit fallback label.live_onlynever reads or writes Goliath’s fallback cache, and reports what it couldn’t search instead.- The shared fallback store holds at most 200 entries. Cached award snapshots expire after 36 hours and public references after 72 hours.
checked_atis when Goliath retrieved a result. It never replaces a supplier’s own timestamps.- Empty cached results and unavailable providers don’t prove that no award seats exist.
Comparing quotes
compare_quotes does exact arithmetic on quotes your assistant already has: total cost, value per point with your own point values, and journeys that mix trains, flights and other legs.
It checks route continuity, timestamps, passenger scope, freshness and connection requirements. A candidate with unknown facts is left out of the ranking rather than filled in with guesses. It never makes a points transfer.
Limits
- Each workspace can make 20
search_travelcalls a day, and each call makes at most four supplier requests. A page with nothing left to search uses no allowance. - Each source has its own quotas, and your assistant’s plan still applies.
- Live award coverage is limited. Confirm the seat, taxes and transfer eligibility with the airline before you move points; transfers usually can’t be undone.
Errors
Errors use the same single JSON block with isError: true:
{ "error": { "code": "VALIDATION_ERROR", "message": "Invalid input",
"issues": [{ "path": ["searches", 0, "tool"], "message": "..." }] } }
Unexpected failures return INTERNAL_ERROR with a reference that matches a log line. No internal detail is returned.
Privacy
Goliath keeps a random workspace ID, sign-in tokens for your assistant, usage counters and supplier health. It keeps no record of your trips. Some search details and results go into shared caches of public prices, with nothing that says who asked.
Selected suppliers receive the search arguments meant for them. Your assistant and each supplier have their own data policies. The privacy page lists everything Goliath stores and for how long.