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
- AlicenseBqualityCmaintenanceMCP 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.554 npm99MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with TripIt travel planning service, allowing users to manage trips, hotel reservations, flights, transport, activities, and documents via natural language.80 npm5-
TDQS
Scored across 8 tools
Most tools target clear actions (search, nearby, photos, reviews, healthcheck), but there is real overlap among ta_get_locations, ta_get_location_details, and ta_web_get_location—all return location details in slightly different modes. The descriptions do clarify batch vs single vs API-key-free fallback, so an agent can disambiguate if it reads carefully.
The ta_ prefix and get/search verb pattern are consistent overall. Minor deviations include ta_web_healthcheck (a noun instead of verb_noun) and the awkward ta_web_get_location placement, plus plural/singular inconsistencies like ta_get_locations vs ta_get_location_details.
Eight tools is a well-scoped size for a TripAdvisor location server. Each tool covers a distinct retrieval need (search, nearby, details, batch, photos, reviews, diagnostics, web fallback) without bloat.
The read-only domain is fully covered: search by name, proximity search, single and batch details, photos, reviews, and a fallback/diagnostic path. No obvious lifecycle operations are missing because the TripAdvisor domain is inherently read-only.