plantrip-mcp-server
Related Servers
Alternatives to plantrip-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables travel planning through natural language, providing weather forecasts, attraction search, itinerary generation, and distance calculations using free APIs.-
- 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.-
- FlicenseNot gradedqualityBmaintenanceConverts natural language travel requests into customizable multi-city itineraries, with tools for planning, editing, and exporting trips across 69 global destinations.-
- AlicenseBqualityBmaintenanceProvides AI agents with a structured API for travel planning, enabling them to read trip data, search places, calculate routes, and create/validate itinerary change proposals that require explicit human approval before being applied.15MIT
- AlicenseAqualityBmaintenanceEnables AI agents to plan trips by searching flights, accommodations, and activities, and managing itineraries collaboratively with role-based permissions.205 npm352 PyPI1MIT
- FlicenseNot gradedqualityDmaintenanceAn AI-powered travel planning assistant that fetches live weather, generates packing suggestions, and provides travel recommendations.-
TDQS
Scored across 14 tools
Each tool targets a distinct combination of resource and action: itinerary creation/retrieval/modification/status, user trip management, packing, expert Q&A, weather, cost, guides, and tour availability/inquiry. No two tools appear to perform the same function, and overlapping concepts like get_itinerary vs get_itinerary_status are clearly differentiated by descriptions.
All tools follow a consistent verb_noun pattern in snake_case: create_itinerary, get_weather_insights, submit_tour_inquiry, etc. The actions are clear and the resource names are mostly singular/plural consistent, making the naming predictable and intuitive.
14 tools is well within the ideal 3-15 range for a travel planning server. Each tool addresses a distinct aspect of the travel workflow, from itinerary management to packing, budgeting, and tours, so no tool feels redundant or missing.
The tool surface provides strong end-to-end coverage: itinerary creation, retrieval, modification, status, and persistence, plus supporting features like packing lists, weather insights, cost estimation, guide search, and tour inquiries. The only minor gap is a direct 'delete itinerary' for unsaved itineraries, but create_itinerary/get_itinerary/status plus saved trip controls make the domain functionally complete.