Agentic Travel Recommendations API
Related Servers
Alternatives to Agentic Travel Recommendations API
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for agentic travel recommendations, exposing tools to retrieve member profiles and personalized travel recommendations with partner-specific rules and policies.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to fetch personalized travel recommendations for loyalty program members while enforcing partner-specific business rules such as category exclusions and recommendation caps. Exposes MCP tools over Streamable HTTP, with a REST endpoint, CLI, and frontend for end-to-end demonstration.-
- FlicenseNot gradedqualityCmaintenanceMCP server for AI-powered travel planning that coordinates flights, hotels, events, weather, currency, and traffic data to generate complete trip itineraries.-
- FlicenseAqualityDmaintenanceAn AI-powered travel planner MCP server enabling flight and hotel search, weather forecasts, point-of-interest discovery, itinerary generation, and budget management.8-
- FlicenseNot gradedqualityAmaintenanceProvides AI-driven, partner-aware travel recommendations with auditability, integrating member context and read-only partner policy rules.-
- AlicenseNot gradedqualityFmaintenanceMCP server for Expedia travel recommendations. Enables LLMs to search hotels, flights, activities, and car rentals using natural language.23Apache 2.0
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: list_members discovers valid IDs, get_member_profile provides detailed member context, and get_recommendations returns the actual recommendations. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: list_members, get_member_profile, get_recommendations. The use of 'list' for collection retrieval and 'get' for single-item retrieval is a standard and predictable convention.
With exactly 3 tools, the server is minimal but well-scoped. Each tool is necessary and supports the core workflow of discovering members, understanding their profile, and generating recommendations. This fits comfortably within the ideal 3-15 range.
The tool surface fully covers the recommendations domain: listing all members, fetching member profiles, and generating personalized recommendations. There are no obvious dead ends or missing operations for the stated purpose.