viator-mcp
Related Servers
Alternatives to viator-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceThis MCP server provides access to TripAdvisor data for planning vacations, enabling users to search for and get details about locations, attractions, restaurants, and hotels through an interactive planning experience.42Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server for travel program search, comparison, and booking via Yourttoo API, optimized for LLMs with token-saving responses.-
- AlicenseNot gradedqualityDmaintenanceEnables searching, browsing, and booking tours and unique travel experiences on GetExperience.com via MCP, with support for both guest payments and B2B partner integrations.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for agentic travel recommendations, exposing tools to retrieve member profiles and personalized travel recommendations with partner-specific rules and policies.-
- FlicenseBqualityFmaintenanceAn MCP server for integrating with the Rezdy Agent API to manage travel marketplace products and bookings. It enables travel agents to search availability, process payments, and manage customer relationships using natural language.162-
- AlicenseNot gradedqualityBmaintenanceMCP server for the Travelpayouts (Aviasales) API. It provides 13 tools for flight search, price calendars, hotel search, and airport/airline/city lookup.57 npmMIT
TDQS
Scored across 11 tools
Each tool targets a distinct resource+action: structured search (vt_search_products) vs free-text (vt_search_freetext), list/get pairs for products, attractions, tags, and destinations, plus availability, locations, exchange rates, and healthcheck. Descriptions actively cross-reference each other (e.g. pointing to vt_list_destinations for ids), making boundaries crystal clear.
All 11 tools use a uniform vt_ prefix with a consistent verb_noun pattern (search_*, get_*, list_*). The only near-deviation is vt_healthcheck, which is still readable and follows the prefix convention.
11 tools is well-scoped for a travel discovery API: search, detail lookups, reference data, and a diagnostic tool. Each tool earns its place without redundancy.
The discovery surface is comprehensive: search, product/attraction detail, availability/pricing, tags, destinations, location resolution, exchange rates, and healthcheck. It lacks booking/checkout operations, but as a read-only discovery set it covers the core workflows with no dead ends.