Summary
A plan you can change without starting the conversation over.
The itinerary is an object with an id, so optimize_itinerary revises the plan that exists instead of generating a second one beside it. Location work runs against Google Maps data, which is what makes attractions within a radius and transport between two points on a date answerable in the same pass as the plan itself.
What it is
Five travel-planning tools backed by Google Maps: itinerary creation from origin, destination, dates, budget and preferences, then optimization of that itinerary, attraction search, transport options and accommodation search.
What you get
- An itinerary built from origin, destination, start and end dates, a budget and stated preferences
- That itinerary re-optimized against criteria you choose, addressed by its itineraryId
- Attractions and points of interest around a location, filtered by category and radius
- Transport options between two points on a given date
- Accommodation in a location for a check-in and check-out date, within a budget
Requirements
A Google Maps API key in `GOOGLE_MAPS_API_KEY`. npx on your PATH.
Setup effort
One command plus a key — npx @gongrzhe/server-travelplanner-mcp, then supply credentials