Cox's Bazar AI Itinerary MCP Server
Related Servers
Alternatives to Cox's Bazar AI Itinerary MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn AI-powered travel planning assistant that fetches live weather, generates packing suggestions, and provides travel recommendations.-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI-assisted travel planning with real-time weather forecasts, place discovery, customized itinerary generation based on interests and budget, and travel distance calculations between cities.-
- AlicenseNot gradedqualityDmaintenanceA comprehensive travel planning copilot that provides geographic data, weather forecasts, transportation details, currency exchange rates, and contextual content to create personalized travel experiences. Enables users to plan itineraries, check real-time conditions, and gather inspirational content for destinations.2 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables weather-based travel advisory generation using wttr.in API, including tools to fetch forecasts, calculate travel risk, and produce structured advisory reports.-
- AlicenseAqualityDmaintenanceEnables comprehensive travel planning by providing tools for flight and accommodation searches, real-time currency exchange, and weather forecasting. It also allows users to calculate estimated trip budgets based on destination, duration, and traveler preferences.56 npm16MIT
- FlicenseNot gradedqualityDmaintenanceEnables travel planning through natural language, providing weather forecasts, attraction search, itinerary generation, and distance calculations using free APIs.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'cox_ai_itinerary' generates a full multi-day itinerary based on dates and duration, while 'get_activity_suggestions' provides activity recommendations based on specific weather and time conditions. There is no overlap in functionality or ambiguity between them.
The naming is mixed: 'cox_ai_itinerary' uses a descriptive noun phrase with underscores, while 'get_activity_suggestions' follows a verb_noun pattern. Although both are readable, they lack a consistent convention, which could confuse agents expecting a uniform style.
With only two tools, the server feels thin for an itinerary planning domain. It lacks essential operations like updating itineraries, fetching historical data, or managing user preferences, which are typical for such a purpose. This minimal set limits functionality and may require agents to work around gaps.
The tool surface is significantly incomplete for itinerary planning. While it covers itinerary generation and activity suggestions, it misses core CRUD operations (e.g., no way to retrieve, modify, or delete itineraries) and lacks integration with user inputs or preferences. This will likely cause agent failures in real-world scenarios.