Wanderlog MCP: agents that edit your trip itineraries
Read and build Wanderlog trips from chat: days, places, notes, hotels, transit, rental cars, budgets and journals land straight in your Wanderlog account.
Project and installation docs
View projecthttps://github.com/shaikhspeare/wanderlog-mcp
Getting a chatbot to draft an itinerary is easy. Copying that draft into your trip app line by line is the tedious part. wanderlog-mcp skips it: the agent creates the trip in your Wanderlog account and fills each day with places and transit tips, so the result is ready to view and share in the app. It’s unofficial, had about 150 stars as of 2026-10-06, and the README links a 14-day Japan trip built entirely by an agent.
What it does
- Read trips:
wanderlog_list_trips,wanderlog_get_tripfor a whole trip or a single day, andwanderlog_get_trip_urlfor a share link. - Build trips:
wanderlog_create_trip,wanderlog_add_placeper day,wanderlog_add_notefor transit and booking tips between stops, andwanderlog_add_checklistfor visas, currency and the like. - Stays and transport:
wanderlog_add_hotel,wanderlog_add_transitfor ferries, buses and trains,wanderlog_add_car_rental, andwanderlog_search_hotelsto compare Airbnb, Expedia, Google and Kayak offers. - Inspiration:
wanderlog_search_guidesandwanderlog_get_guideread public user-written guides. - Budget and journal: log and edit expenses, add dated journal entries, and shift a whole trip with
wanderlog_update_trip_dates.
Who it’s for
- Wanderlog users who want Claude to produce a first draft they can then tweak by hand.
- Whoever books for the family or a group and needs a multi-day, multi-city plan in one pass.
Setup
Needs Node.js 22+ and a Wanderlog account. Wanderlog has no public API, so you first copy the connect.sid session cookie from your browser’s developer tools (the README walks through it), then add it to Claude Code:
claude mcp add wanderlog-mcp npx wanderlog-mcp \
--env WANDERLOG_COOKIE="s%3A...your value here..."
Our take
It’s the only server we found in the travel space that writes itineraries rather than just reading data, and it’s actively maintained: recent releases added automatic retry on rate limits, duplicate-safe custom lists and hotel price comparison. The trade-offs are plain. It signs in with a session cookie valid for about a year, which works like your password; leak it and someone else can edit every trip. Automating a private API may also breach Wanderlog’s terms, and any change on their side can break it. wanderlog_delete_section removes a whole list, so have your client ask before running it. MIT licensed.