io.github.chrischallPublished by GitHub account chrischallv2.2.0Updated Nov 5, 2026
Search Viator tours and activities — products, availability, attractions, destinations.
Local MCP server for the Viator Partner API that lets an assistant search tours, activities, attractions and destinations, and check availability and pricing.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
MCP server for the Viator Partner API (v2) — search tours, activities and experiences for Claude. Search the catalog with structured filters or free text, get product details and availability schedules, browse attractions and destinations, all over stdio.
Developed and maintained by AI (Claude Code). Use at your own discretion.
Get a key by signing up as a Viator affiliate at partnerresources.viator.com — the Basic Access tier is free. This server targets that tier: read-only search/content/availability; no booking endpoints (product results carry a productUrl for booking on viator.com, tagged with your affiliate id).
All tools are read-only. vt_search_products and vt_search_freetext accept compact: true for slim summaries (code, title, price, rating, booking URL) instead of full records.
Viator rate-limits per endpoint on a rolling 10-second window and answers 429/503 with Retry-After; the client honors it (one retry) and the response cache absorbs repeated identical calls.
The API surface this server is coded against is pinned in docs/VIATOR-API.md.
MIT
Source: README.md at commit 606ee4d
Search Viator tours, activities and experiences with structured filters (destination, tags, price, dates, rating, duration). Returns product summaries with pricing and booking URLs. Use vt_list_destinations to find destination ids and vt_list_product_tags for tag ids.
sorttagsviewcountflagsorderstartcurrencyend_datemax_ratingmin_ratingstart_date+6 moreGet full details for one Viator product by product code — description, inclusions/exclusions, itinerary, product options, cancellation policy, booking URL, review summary.
viewproduct_coderequiredcampaign_valueList all Viator product tags (tag id → names in every locale, with parent-tag hierarchy). Use tag ids to filter vt_search_products. Reference data — cached.
viewList attractions (landmarks, museums, points of interest) in a Viator destination, including the product codes mapped to each attraction. Use vt_list_destinations to find destination ids.
sortviewcountstartcampaign_valuedestination_idrequiredGet details for one Viator attraction by id — name, destination, opening hours, review summary, mapped product codes, and the attraction URL.
viewattraction_idrequiredcampaign_valueGet the availability schedule and pricing for a Viator product — seasons, days of week, start times, unavailable dates, and per-age-band pricing for every product option. NOTE: prices are in the SUPPLIER's currency (see the currency field); convert with vt_get_exchange_rates.
viewproduct_coderequiredFree-text search across Viator products, attractions, and destinations (e.g. "colosseum underground tour"). The fastest way to find things when you don't have a destination id yet.
sortviewcountorderstartcurrencyend_datemax_pricemin_pricemin_ratingstart_datedestination+3 moreList every Viator destination (cities, regions, countries) with ids, parent hierarchy, IATA codes, time zones, and coordinates. Use the destinationId with vt_search_products / vt_search_attractions. Reference data — cached.
viewcampaign_valueResolve Viator location references (e.g. "LOC-...", meeting points, pickup points from product details) to names, addresses, and coordinates. Up to 500 references per call. Reference data — cached.
viewlocation_refsrequiredGet exchange rates between currencies Viator supports — needed to convert supplier-currency prices from vt_get_availability_schedule. Reference data — cached.
viewsource_currenciestarget_currenciesVerify credentials and upstream reachability
Resolves the credential the way real tools do, then makes one authenticated request to api.viator.com. Reports which source supplied the credential, whether api.viator.com accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a api.viator.com-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.
Takes no parameters.
80% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Declare a license in the repository or the registry entry.
{ "mcpServers": { "viator": { "command": "npx", "args": ["-y", "@chrischall/viator-mcp"], "env": { "VIATOR_API_KEY": "your-viator-partner-api-key" } } }}npm installnpm test # vitest; no real network callsnpm run build # tsc + esbuild bundle