Wanderlog MCP

What shaikhspeare/wanderlog-mcp MCP server does

shaikhspeare/wanderlog-mcp MCP server connects an MCP-compatible agent to a Wanderlog account for itinerary reading and editing. It covers trip discovery, detailed itinerary retrieval, share links, forwarding addresses, destination place search, public travel-guide lookup, and hotel searches. Editing operations can create trips and add or remove itinerary items such as places, notes, hotels, transport legs, car rentals, checklists, expenses, and journal entries.

The server is suited to conversational trip planning. An agent can create a trip with a destination and date range, populate days with places and practical notes, add transportation or lodging details, and later adjust dates or rename day headings. It also supports reviewing and maintaining budget expenses and travel-journal content.

How it works

The project runs as a local stdio MCP server and uses a Wanderlog browser session cookie for authentication because Wanderlog does not provide a public API. The required cookie is named connect.sid. It is copied from the browser's developer tools after signing in to Wanderlog, then passed to the MCP process as an environment variable.

The cookie grants the same account access available in the Wanderlog website, so it should be handled like a password. The README states that the cookie remains on the user's machine and is generally valid for about a year. Startup authentication checks can identify expired cookies, and a transient startup failure receives a shared retry on the first tool call. Rapid itinerary edits are retried with backoff when Wanderlog rate-limits requests.

Setup and configuration

shaikhspeare/wanderlog-mcp MCP server requires Node.js 22 or newer, a Wanderlog account, and an MCP client that supports stdio servers. The repository documents use with Claude Code and lists Claude Desktop, OpenAI Codex, Cursor, and VS Code as compatible MCP hosts.

Configure the server with the WANDERLOG_COOKIE environment variable. To obtain its value, sign in at wanderlog.com, open browser developer tools, inspect cookies for https://wanderlog.com, and copy the value for connect.sid. In Chrome or Edge, this is under Application and Storage; in Firefox, it is under Storage and Cookies. The cookie is HttpOnly, so it cannot be read with document.cookie.

A package-runner configuration can invoke the published wanderlog-mcp package with Node.js. The client configuration must supply the cookie value; no API key is documented.

Tools and capabilities

The available tools include:

• List trips, retrieve a complete itinerary or one day, and return a shareable Wanderlog URL or trip import email.
• Search places near a destination, public user-written guides, and hotel offers from Airbnb, Expedia, Google, and Kayak.
• Create trips and add places, notes, hotels, ferries, buses, trains, rental cars, and checklists.
• Find and replace note content across notes, place annotations, and checklist titles or items.
• Add, edit, list, and remove budget expenses with optional filters and place links.
• Annotate or remove places, change trip dates, and rename day headings.
• List, add, edit, and remove journal stops, including journal summaries and date or time data.

Limitations and notes

The server depends on a valid Wanderlog browser session cookie rather than a public API credential. Losing or expiring that session requires obtaining a new cookie. The cookie provides account-level access, so it should not be shared or committed to configuration files. Hotel results come from Wanderlog's aggregator and include vendor comparisons, while guide retrieval applies to public Wanderlog guides. The project requires a local Node.js runtime and an MCP-compatible client; the provided material does not describe a hosted endpoint.