tripadvisor-mcp
Related Servers
Alternatives to tripadvisor-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to search Tripadvisor hotels, restaurants, and attractions and fetch full review streams through the Apify MCP server. Integrates with Claude, ChatGPT, Cursor, and other tools via natural language.-
- 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
- AlicenseBqualityDmaintenanceMCP server that enables LLMs to interact with Tripadvisor API, supporting location data, reviews, and photos through standardized MCP interfaces564MIT
- FlicenseBqualityCmaintenanceEnables comprehensive travel and hospitality operations including parallel hotel price comparison, restaurant discovery and reservations, multi-modal transit directions, and cross-platform place reviews.201-
- AlicenseAqualityFmaintenanceEnables LLMs to perform travel-related tasks by interacting with Google Maps and travel planning services including location search, place details, and travel time calculations.525 npm98MIT
- AlicenseNot gradedqualityBmaintenanceEnables interaction with TripIt travel planning service, allowing users to manage trips, hotel reservations, flights, transport, activities, and documents via natural language.103 npm5AGPL 3.0
TDQS
Scored across 8 tools
Most tools target distinct operations (search by name, search nearby, photos, reviews, batch details). The main overlap is between ta_web_get_location and ta_get_location_details, which both retrieve location details; the description clarifies one is a fallback, but an agent could still misselect if not reading carefully.
All names use snake_case with a consistent ta_ prefix. Most follow verb_noun (get, search), but ta_web_healthcheck is a noun and the ta_web_* vs ta_* split creates a minor stylistic variation.
Eight tools is well-scoped for a read-only TripAdvisor client. Each tool covers a distinct capability (search, nearby, details, photos, reviews, batch, fallback, diagnostics) without obvious redundancy.
The surface covers the full read lifecycle for TripAdvisor locations: discovery (search/nearby), detail retrieval (single and batch), sub-resources (photos, reviews), and a fallback path for API key issues. No obvious missing operations for a public-data client.