create_itinerary
Creates a personalized travel itinerary based on user preferences
LABSCO 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
USE CASES
01
Turning a rough travel idea into a day-by-day plan
Origin, destination, dates, budget and preferences produce an itinerary with an id — so the follow-up request revises that plan instead of generating a second one.
02
Working out how to get between two stops
Transport options for a specific date, which is the part of a plan that changes depending on the day of the week.
03
Finding somewhere to stay inside the budget
Accommodation for a check-in and check-out date in a location, filtered by what you are willing to spend.
04
Filling a free afternoon near where you are staying
Attractions within a radius of a point, narrowed by category, so the search is bounded by how far you are willing to walk.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_accommodations
Searches for accommodation options in a specified location
get_transport_options
Retrieves available transportation options between two points
optimize_itinerary
Optimizes an existing itinerary based on specified criteria
search_attractions
Searches for attractions and points of interest in a specified location
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. The installed package exposes create_itinerary, get_accommodations, get_transport_options, optimize_itinerary and search_attractions; the documented Google Maps tools (searchPlaces, getPlaceDetails, calculateRoute, getTimeZone) do not exist.
Requires
- npx on PATH
- GOOGLE_MAPS_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @gongrzhe/server-travelplanner-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"travel-planner": {
"command": "npx",
"args": [
"@gongrzhe/server-travelplanner-mcp"
],
"env": {
"GOOGLE_MAPS_API_KEY": "<YOUR_GOOGLE_MAPS_API_KEY>"
}
}
}
}
