Log inSubmit server
Viator MCP logo

Viator MCP

Search Viator tours, activities, attractions, destinations, product details, and availability through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Viator MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "viator-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/viator-mcp"
      ],
      "env": {
        "VIATOR_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The viator-mcp MCP server connects AI clients to Viator Partner API v2 for read-only travel catalog searches and reference lookups. It supports structured product searches, free-text queries, product details, availability schedules, attractions, destinations, locations, tags, and exchange rates over stdio. Use it when an agent needs to discover Viator experiences or inspect booking information without creating reservations. A Viator Partner API key is required, and results include Viator booking URLs rather than booking actions.

Use cases

  • Search Viator products by structured filters
  • Find tours and activities with free-text queries
  • Retrieve product availability schedules
  • Browse attractions and destination reference data
  • Check Viator API authentication status

Key features

  • Structured product search
  • Free-text experience search
  • Product details and availability
  • Attraction and destination lookup
  • Read-only Viator API access
  • Caching and rate-limit retry handling

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 35d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @chrischall/viator-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads2.3kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.

How Viator MCP works

What the viator-mcp MCP server does

The viator-mcp MCP server exposes the Viator Partner API v2 through MCP tools. It is designed for read-only discovery and content retrieval rather than transaction processing. Agents can search tours, activities, and experiences using structured filters or free text, then inspect individual products and their availability schedules.

The server also covers Viator reference data and attractions. It can find attractions, retrieve attraction details, list destinations, retrieve locations, list product tags, and obtain exchange rates. Product search results can include a Viator booking URL carrying the affiliate identifier, but the server does not provide booking endpoints.

How it works

The server communicates over stdio. An MCP client starts the package with npx, and the process uses the VIATOR_API_KEY environment variable to authenticate requests to Viator. The key is sent as the exp-api-key header expected by the Partner API.

Search tools support a compact option. When enabled for product or free-text searches, responses are reduced to fields such as the product code, title, price, rating, and booking URL instead of returning full records.

The viator-mcp MCP server caches identical read requests for a configurable period. Reference responses, including destinations, tags, locations, and exchange rates, have a separate cache duration. When Viator returns rate-limit or temporary-service responses with Retry-After, the client observes that value and performs one retry.

Setup and configuration

Add the server to an MCP client using the npx -y @chrischall/viator-mcp command and provide a Viator Partner API key in the environment. The Basic Access tier is identified as sufficient for the server’s read-only search, content, and availability operations.

Supported configuration variables are:

  • VIATOR_API_KEY: required Partner API key.
  • VIATOR_API_BASE_URL: optional API host; the default is production, while the documented sandbox value is https://api.sandbox.viator.com/partner.
  • VIATOR_LANGUAGE: optional response language, defaulting to en-US.
  • VIATOR_CACHE_TTL: optional cache duration in seconds for identical reads; the default is 60, and 0 disables it.
  • VIATOR_STATIC_CACHE_TTL: optional cache duration for reference data; the default is 3600 seconds.

Tools and capabilities

The available tools are grouped as follows:

  • Products: vt_search_products, vt_get_product, and vt_list_product_tags.
  • Search: vt_search_freetext.
  • Attractions: vt_search_attractions and vt_get_attraction.
  • Availability: vt_get_availability_schedule.
  • Reference: vt_list_destinations, vt_get_locations, and vt_get_exchange_rates.
  • Health: vt_healthcheck.

The health check reports whether the API key was found, whether Viator accepted it, and what correction may be needed. It can help distinguish an empty search result from an authentication problem.

Limitations and notes

All tools are read-only. The server does not create bookings; agents must use the returned productUrl to continue booking on viator.com. Viator applies endpoint rate limits over rolling 10-second windows, so callers should account for throttling even though the client handles one retry and caches repeated requests. The API surface is pinned to the version documented by the project, and local development uses tests without real network calls.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Viator MCP

viator-mcp is an MCP server that connects AI clients to the Viator Partner API v2. Its main tools search products and free text, retrieve product details and availability, browse attractions and destinations, access reference data, and check API authentication. All operations are read-only, with booking continued through returned Viator URLs.

Install it through an MCP client by running `npx -y @chrischall/viator-mcp` and setting `VIATOR_API_KEY` in the server environment. The README provides a JSON configuration using the `viator` server name and the stdio transport.

It requires a Viator Partner API key in `VIATOR_API_KEY`. The project points developers to Viator’s partner resources site and states that the Basic Access tier supports its read-only search, content, and availability use cases.

No, it cannot create bookings. The server exposes read-only Viator operations, and product results provide a `productUrl` for continuing the booking process on viator.com.

Yes, it can be configured in Cursor as a standard stdio MCP server. Provide the `npx` command, the `@chrischall/viator-mcp` package argument, and the required `VIATOR_API_KEY` environment variable.

Related MCP servers

All in Travel & Transportation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewViator MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/viator-mcp?style=directory)](https://allmcps.com/mcp/viator-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/viator-mcp"><img src="https://allmcps.com/api/badge/viator-mcp?style=directory" alt="Viator MCP on AllMCPs" /></a>