wanderlog-mcp

Lists all Wanderlog trips in the authenticated user's account (owned and shared-with-you).

Returns a compact list with title, dates, place count, and trip_key. Use this tool first when the user mentions a trip by name but you don't have its trip_key yet — the key is required by wanderlog_get_trip and wanderlog_search_places.

Each line includes a [key: ...] suffix — extract that key for downstream tool calls.

Returns the itinerary for one Wanderlog trip: the hotels list, the "places to visit" list, and each day's scheduled places.

Use concise format for summarizing or answering questions about a trip in natural language. Use detailed format when the user asks for specific info like addresses, phone numbers, or hotel check-in/out dates.

If you don't know the trip_key, call wanderlog_list_trips first to find it.

Returns the wanderlog.com URL for a trip so the user can open it in a browser.

Three link variants are available via the mode parameter:

• edit (default) — full-permission link for the owner

• view — read-only link that's safe to share with anyone

• suggest — suggest-mode link where collaborators can propose changes

If you don't know which mode the user wants, default to edit.

Search for real-world places (restaurants, attractions, hotels, parks, landmarks) near the destination of a Wanderlog trip. Returns candidate results with names and short descriptions.

Use this to resolve user requests like "find a good coffee shop in Queenstown" into specific place candidates. Results are geographically biased toward the trip's location, not global.

If the user wants to add a place to a trip, call this first with concise format to present options, then call again with detailed format to get place_ids for downstream actions.

Creates a new Wanderlog trip for the given destination and date range. The trip is created empty (no places yet) with one pre-generated day section per day in the range.

After creating a trip, populate each day using ALL of these tools together — places alone make a flat list, but notes and checklists are what make an itinerary actually useful:

1. wanderlog_add_place — add attractions, restaurants, and activities

2. wanderlog_add_note — add between places for transit directions, practical tips, time warnings, or local recommendations (e.g. "Walk 10 min south along the river to the next stop" or "Closed Mondays — check hours before visiting")

3. wanderlog_add_hotel — add accommodation with check-in/check-out dates

4. wanderlog_add_checklist — add a packing list to the trip, or per-day task lists (e.g. "Day 1 prep: print tickets, charge camera, pack umbrella")

A good itinerary has notes after most places — think of them as the connective tissue that turns a list of pins on a map into a real travel plan.

Returns the new trip key so you can reference it in subsequent tool calls.

Adds a place to a Wanderlog trip. Searches for the place near the trip's destination, picks the best match, and inserts it into either a specific day or the general "Places to visit" list.

PREFERRED: Use the "note" parameter to attach practical context directly to each place — transit directions, what to order, booking tips, time guidance. This is better than a separate wanderlog_add_note call because the note lives on the place itself in the itinerary. Use the "start_time" and "end_time" parameters to give the place a scheduled time window.

Use standalone wanderlog_add_note only for freestanding commentary between places (neighborhood context, multi-stop transit, day-level tips that aren't about a specific place).

Returns a confirmation including the resolved place name and where it was added.

Adds a hotel booking to a Wanderlog trip with check-in and check-out dates. If the trip does not yet have a "Hotels and lodging" section, one is created automatically.

Returns confirmation with the resolved hotel name and the booking window.

Adds a text note to a Wanderlog trip. Notes appear inline between places in a day, acting as the connective tissue of the itinerary. Every well-built day should have notes between stops.

When to add a note (do this after adding each place or group of places):

• How to get there: "Walk 15 min along the South Bank, or take the Jubilee line one stop"

• Practical tips: "Book tickets online at least 2 days ahead — sells out in summer"

• Food/drink recs: "Try the salt beef bagel at Beigel Bake — cash only, open 24hrs"

• Time guidance: "Budget 2-3 hours here. Open 10am-6pm, closed Tuesdays"

• Neighborhood context: "This area is great for wandering — no rush, just explore the lanes"

Returns a confirmation of where the note was added.

Adds a checklist to a Wanderlog trip. Each item starts unchecked and can be ticked off in the Wanderlog app.

Add at least one checklist per trip. Common patterns:

• On the trip (no day): a packing list or "before departure" checklist

• On day 1: an arrival-day checklist ("pick up Oyster card", "check into hotel", "buy SIM")

• On specific days: day-of tasks ("bring swimsuit", "charge camera", "carry cash for market")

Returns a confirmation including the checklist title and item count.

Updates an existing place in a Wanderlog trip with an inline note, start/end time, or both. Use this to enrich places that were already added — set practical context, scheduled times, or both in one call.

At least one of note, start_time, or end_time must be provided.

The place is resolved by natural-language reference (same syntax as wanderlog_remove_place). If ambiguous, returns a disambiguation list without making changes.

Adds a budget expense to a Wanderlog trip. Expenses appear in the trip's budget tracker and can be linked to a specific place in the itinerary.

Use this after adding places to give the trip a cost dimension — estimated meal costs, entrance fees, transport passes, etc. Linked expenses show up on the place in Wanderlog's budget view.

Returns confirmation with the expense amount and description.

Removes a place (or flight, train, hotel — any block) from a Wanderlog trip based on a natural-language reference.

Supported reference forms:

• Exact or partial name: "Queenstown Gardens", "Gardens"

• Role keywords: "the hotel", "the flight", "the train"

• Day filter: "Queenstown Gardens on May 4" or "... on day 3"

• Ordinal prefix (for duplicates): "1st Queenstown Gardens", "second X", "last X"

• Combined: "2nd Queenstown Gardens on May 4"

If the reference is ambiguous (multiple places match), the tool returns a numbered list of candidates and does NOT make any change. Re-call with an ordinal prefix ("1st X", "2nd X") or a more specific filter to pick the one you want.

Changes the date range of an existing Wanderlog trip. Preserves content on days that remain in the new range (they're kept in place with their blocks intact), adds empty day sections for newly-included days, and removes day sections for days no longer in range.

SAFETY: If the new range would delete days that currently contain places or notes, the tool refuses by default and returns a list of the content that would be lost. Pass force: true to override, or move the content to other days first.

Does not affect the Hotels, Flights, Transit, or Places-to-visit sections — only the per-day sections are added/removed.