Skip to content
Back to search

wanderlog-mcp

MCP server for Wanderlog — build and edit trip itineraries through conversation

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/shaikhspeare/wanderlog-mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/shaikhspeare/wanderlog-mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/shaikhspeare--wanderlog-mcp/badge.svg)](/listings/shaikhspeare--wanderlog-mcp)

HTML

<a href="/listings/shaikhspeare--wanderlog-mcp"><img src="/api/listings/shaikhspeare--wanderlog-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Step 1 — Get your Wanderlog session cookie

Wanderlog doesn't have a public API, so wanderlog-mcp authenticates using your browser session cookie (`connect.sid`). It's valid for roughly a year and never leaves your machine.

**Treat it like a password** — it grants the same access you have in the Wanderlog UI.

Chrome / Edge

1. Go to [wanderlog.com](https://wanderlog.com) and log in 2. Press `F12` to open DevTools 3. Click the **Application** tab 4. In the left sidebar expand **Storage → Cookies → https://wanderlog.com** 5. Find the row where **Name** is `connect.sid` 6. Click the row, then double-click the **Value** cell and copy the full string — it starts with `s%3A` and is ~100 characters long

Firefox

1. Go to [wanderlog.com](https://wanderlog.com) and log in 2. Press `F12` to open DevTools 3. Click the **Storage** tab 4. In the left sidebar expand **Cookies → https://wanderlog.com** 5. Find `connect.sid` in the table, click it, and copy the **Value**

> **Why can't I use `document.cookie` in the console?** > Wanderlog sets `connect.sid` with the `HttpOnly` flag, which deliberately blocks JavaScript from reading it (XSS protection). DevTools bypasses this restriction — that's why it works and the console doesn't.

Step 2 — Configure your MCP client

Claude Code

claude mcp add wanderlog-mcp npx wanderlog-mcp \
  --env WANDERLOG_COOKIE="s%3A...your value here..."

Claude Desktop

Edit `claude_desktop_config.json`:

- **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json` - **Windows:** `%APPDATA%\Claude\claude_desktop_config.json` - **Linux:** `~/.config/Claude/claude_desktop_config.json`

{
  "mcpServers": {
    "wanderlog": {
      "command": "npx",
      "args": ["wanderlog-mcp"],
      "env": {
        "WANDERLOG_COOKIE": "s%3A...your value here..."
      }
    }
  }
}

Restart Claude Desktop after saving.

Cursor

Settings → MCP → Add server, or edit `~/.cursor/mcp.json`:

{
  "mcpServers": {
    "wanderlog": {
      "command": "npx",
      "args": ["wanderlog-mcp"],
      "env": {
        "WANDERLOG_COOKIE": "s%3A...your value here..."
      }
    }
  }
}

VS Code (GitHub Copilot)

Add to your workspace `.vscode/mcp.json`:

{
  "servers": {
    "wanderlog": {
      "type": "stdio",
      "command": "npx",
      "args": ["wanderlog-mcp"],
      "env": {
        "WANDERLOG_COOKIE": "s%3A...your value here..."
      }
    }
  }
}

OpenAI Codex

Edit `~/.codex/config.toml`:

[mcp_servers.wanderlog]
command = "npx"
args = ["wanderlog-mcp"]

[mcp_servers.wanderlog.env]
WANDERLOG_COOKIE = "s%3A...your value here..."

Run `/mcp` inside Codex to confirm the server loaded.

Smithery (one-click install)

npx @smithery/cli install wanderlog-mcp --client claude

Step 3 — Verify

Ask your agent: _"What trips do I have in Wanderlog?"_

It should call `wanderlog_list_trips` and return your account's trips. If it fails, see [Troubleshooting](#troubleshooting) below.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 348 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # wanderlog-mcp
  2. [![npm](https://img.shields.io/npm/v/wanderlog-mcp)](https://www.npmjs.com/package/wanderlog-mcp)
  3. [![npm downloads](https://img.shields.io/npm/dm/wanderlog-mcp)](https://www.npmjs.com/package/wanderlog-mcp)
  4. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
  5. [![Node.js](https://img.shields.io/badge/node-%3E%3D22-brightgreen)](https://nodejs.org/)
  6. [![Coverage Status](https://coveralls.io/repos/github/shaikhspeare/wanderlog-mcp/badge.svg?branch=main)](https://coveralls.io/github/shaikhspeare/wanderlog-mcp?branch=main)
  7. An MCP server that lets Claude (or any MCP-compatible agent) view and build [Wanderlog](https://wanderlog.com) trip itineraries through conversation.
  8. Instead of clicking through the Wanderlog UI to plan a trip, you just ask:
  9. > _"Create a 14-day Japan Golden Route trip — Tokyo, Hakone, Kyoto, Nara, and Osaka."_
  10. The agent calls the tools, interleaves places and notes for each day, adds hotel blocks, ferries, buses, trains, rental cars, and checklists, and you end up with a fully populated Wanderlog trip in a few minutes.
  11. **See a real example:** [14-day Japan Golden Route](https://wanderlog.com/view/dmvegdhqsa/japan-golden-route--tokyo--hakone--kyoto--nara--osaka) — built entirely by an AI agent using this MCP server.
  12. ## What's New (Unreleased)
  13. - Place and custom-list ordering tools support explicit 1-based positions with safe boundary validation.
  14. - `wanderlog_move_place` moves an existing place between custom lists and itinerary days while preserving its complete metadata.
  15. - Custom-list lifecycle operations now reject duplicate or ambiguous section headings instead of silently changing the first match.
  16. - `wanderlog_search_hotels` — search Wanderlog's hotel aggregator across airbnb, expedia, google, and kayak. Returns ranked offers with per-vendor price comparison and faceted filter discovery so the LLM never has to memorise Wanderlog's internal enum values.
  17. - A failed startup authentication probe now gets one shared retry on the first tool call, allowing valid sessions to recover from a transient network or proxy error without restarting the server.
  18. - `wanderlog_add_place` accepts an optional `place_id`, so `wanderlog_search_places` (`response_format: "detailed"`) now has somewhere to send its results — pass the id straight through to add the exact candidate when a name matches multiple branches or the wrong city, instead of hoping the top autocomplete match is right.
  19. - `wanderlog_annotate_place` now replaces a place's existing note instead of appending the new text to it, including notes that contain images.
  20. - Place lookups no longer fail with "Place not found" when Wanderlog's autocomplete returns an entry with no place ID ahead of the real result. This affected adding places, hotels, journal stops and transit endpoints, and `wanderlog_search_places` listed those entries as `undefined`.
  21. ## What's New in v0.3.1
  22. - Wanderlog rate-limits rapid edits — burst mutations (an LLM building a full itinerary) now retry automatically with backoff instead of failing with an opaque "Submit op timeout".
  23. - Rate-limit rejections that can't be retried surface as a clear error instead of a 10-second hang.
  24. - New day sections created by `wanderlog_update_trip_dates` now match Wanderlog's native section shape exactly.
  25. ## What's New in v0.3.0
  26. - `wanderlog_search_guides` + `wanderlog_get_guide` — discover and read user-written Wanderlog travel guides. The LLM can ask "what guides exist for Vietnam?" and pull full itineraries to use as inspiration.
  27. - `wanderlog_remove_note` — remove standalone note blocks by natural-language reference.
  28. - `wanderlog_edit_note` — find-and-replace across note blocks, place annotations, and checklist titles/items.
  29. - Detailed mode no longer truncates place notes or note blocks — guides and itineraries render their full commentary.
  30. - Fixes: notes containing embeds no longer render as `[object Object]`; place references now match across hyphen/dash differences (e.g. `"Roppongi Hills - Tokyo City View"`).
  31. ## What's New in v0.2.0
  32. - `wanderlog_rename_day` — replace auto-generated day headings (e.g. `"Barcelona"`) with descriptive ones (`"Arrival — Feria de Abril"`). Pass `""` to reset back to the default.
  33. - Tools table now documents `wanderlog_annotate_place` and `wanderlog_add_expense` (shipped previously, missing from v0.1.0 docs).
  34. ## What's New in v0.1.0
  35. - Full itinerary building: places, notes, hotels, and checklists in a single conversation
  36. - `wanderlog_search_places` — find real-world places near any destination using Wanderlog's place database
  37. - `wanderlog_add_note` — interleave transit tips, booking info, and local advice between places
  38. - `wanderlog_add_checklist` — pre-trip and per-day checklists (visa, currency, timed-entry tickets)
  39. - MCP server instructions injected at startup so Claude builds complete itineraries automatically
  40. - Startup auth probe — catches expired cookies immediately instead of failing mid-conversation
  41. ## Example Prompts
  42. ```
  43. "What trips do I have in Wanderlog?"
  44. ```
  45. ```
  46. "Create a 7-day itinerary for Lisbon starting June 1 — include restaurants, day trips,
  47. and a hotel near the waterfront."
  48. ```
  49. ```
  50. "Add a day trip to Sintra on day 3 of my Lisbon trip."
  51. ```
  52. ```
  53. "I'm spending 5 days in Tokyo — build me a full itinerary with museum visits, ramen spots,
  54. and a ryokan in Shinjuku."
  55. ```
  56. ```
  57. "Look at my Barcelona trip and add practical notes for getting between each place."
  58. ```
  59. ```
  60. "Add a pre-trip checklist to my Paris trip — visa, currency, offline maps, travel insurance."
  61. ```
  62. ```
  63. "Move my Rome trip back by two weeks."
  64. ```
  65. ```
  66. "Give me the shareable link to my Kyoto itinerary."
  67. ```
  68. ```
  69. "Remove the Colosseum from day 2 of my Rome trip."
  70. ```
  71. ## Tools
  72. | Tool | What it does |
  73. | ------------------------------------- | ------------------------------------------------------------------------------------------------- |
  74. | `wanderlog_list_trips` | List trips in your account |
  75. | `wanderlog_get_trip` | View a full itinerary, or filter to a single day |
  76. | `wanderlog_get_trip_url` | Get a shareable wanderlog.com link |
  77. | `wanderlog_get_trip_forwarding_email` | Get a trip's `trip+<id>@wanderlog.com` import address |
  78. | `wanderlog_search_places` | Find real-world places near a trip's destination |
  79. | `wanderlog_search_guides` | List user-written travel guides for a destination, with fallback suggestions when none exist |
  80. | `wanderlog_get_guide` | Read the full content of a public Wanderlog guide (sections, places, notes) |
  81. | `wanderlog_search_hotels` | Search Wanderlog's hotel aggregator (airbnb/expedia/google/kayak) with per-vendor deal comparison |
  82. | `wanderlog_create_trip` | Create a new trip with destination + date range |
  83. | `wanderlog_add_place` | Add a place to a specific day or general list |
  84. | `wanderlog_add_note` | Add a note (transit tips, booking info, local advice) |
  85. | `wanderlog_edit_note` | Find-and-replace text in notes, place annotations, and checklists |
  86. | `wanderlog_remove_note` | Remove a standalone note block by natural-language reference |
  87. | `wanderlog_add_hotel` | Add a hotel booking with check-in/check-out dates |
  88. | `wanderlog_add_transit` | Add a ferry, bus, or train leg (carrier, from/to, dates/times) to the shared Transit section |
  89. | `wanderlog_add_car_rental` | Add a rental car with pick-up/drop-off locations and times |
  90. | `wanderlog_add_checklist` | Add a pre-trip or per-day checklist |
  91. | `wanderlog_set_checklist_item` | Tick or untick a checklist item by its text |
  92. | `wanderlog_add_expense` | Log a budget expense (amount, category, currency), optionally linked to a place |
  93. | `wanderlog_list_expenses` | List budget expenses, optionally filtered by description / date / amount / currency |
  94. | `wanderlog_remove_expense` | Remove a budget expense by description (with optional date / amount / currency filters) |
  95. | `wanderlog_edit_expense` | Change a budget expense's description, amount, currency, category, or date |
  96. | `wanderlog_annotate_place` | Update an existing place with a note, start/end time, or both |
  97. | `wanderlog_remove_place` | Remove a place by natural-language reference |
  98. | `wanderlog_move_block` | Move an existing place or reservation block within its current section |
  99. | `wanderlog_move_place` | Move an existing place to another undated list or itinerary day, preserving its metadata |
  100. | `wanderlog_reorder_places` | Reorder places within one list or itinerary day using explicit 1-based positions |
  101. | `wanderlog_reorder_sections` | Reorder custom lists using 1-based positions |
  102. | `wanderlog_update_trip_dates` | Change a trip's date range |
  103. | `wanderlog_rename_day` | Rename a day's heading (e.g. `"Barcelona"` → `"Arrival — Feria de Abril"`) |
  104. | `wanderlog_add_section` | Create a uniquely named custom list, optionally after another section |
  105. | `wanderlog_update_section` | Rename a custom list while preventing duplicate headings |
  106. | `wanderlog_delete_section` | Permanently delete a custom list and all blocks inside it |
  107. | `wanderlog_list_journal` | List journal (travelogue) stops, optionally filtered by title or date |
  108. | `wanderlog_add_journal` | Add a journal stop: a place + date/time + text entry |
  109. | `wanderlog_edit_journal` | Edit a journal stop's title, text, or date/time (or the journal summary) |
  110. | `wanderlog_remove_journal` | Remove a journal stop by title (with an optional date filter) |
  111. ### Managing custom lists
  112. Custom sections are undated lists outside Wanderlog's protected default/system sections.
  113. Create one with `wanderlog_add_section`, rename it with `wanderlog_update_section`, and delete
  114. it with `wanderlog_delete_section`. Deleting is destructive: every block in that section is
  115. removed. Section headings used by these tools must be unique (matching ignores case); ambiguous
  116. or duplicate targets return errors without submitting a mutation.
  117. ### Moving places between lists and days
  118. `wanderlog_move_place` moves the existing place block rather than creating a copy, so its note,
  119. start/end time, images, booking fields, and unknown metadata travel with it. Supply exactly one
  120. destination: `target_section` for an undated custom list (or `Places to visit`), or `target_day`
  121. for `day 2`, `May 4`, or an ISO date such as `2026-05-04`.
  122. An optional `position` is 1-based among places at the destination; omit it to append after the
  123. last place. If a place name occurs more than once, qualify `place_ref` with an ordinal and/or
  124. day, for example `2nd Starbucks on day 3`. Ambiguous places, duplicate section headings,
  125. unknown days, and out-of-range positions return errors without submitting a mutation.
  126. ### Reordering places and custom lists
  127. `wanderlog_reorder_places` changes one place's 1-based position within exactly one `section` or
  128. `day`. `wanderlog_reorder_sections` similarly changes one custom list's position among custom
  129. lists only. Both operations move the original object intact; they do not rebuild or truncate
  130. metadata. Position 1 selects the first place/list, and the current count selects the last.
  131. ## Prerequisites
  132. - **Node.js 22 or newer**
  133. - **A [Wanderlog](https://wanderlog.com) account**
  134. - An MCP-compatible client: Claude Code, Claude Desktop, OpenAI Codex, Cursor, VS Code, or any stdio MCP host
  135. ## Setup
  136. ### Step 1 — Get your Wanderlog session cookie
  137. Wanderlog doesn't have a public API, so wanderlog-mcp authenticates using your browser session cookie (`connect.sid`). It's valid for roughly a year and never leaves your machine.
  138. **Treat it like a password** — it grants the same access you have in the Wanderlog UI.
  139. #### Chrome / Edge
  140. 1. Go to [wanderlog.com](https://wanderlog.com) and log in
  141. 2. Press `F12` to open DevTools
  142. 3. Click the **Application** tab
  143. 4. In the left sidebar expand **Storage → Cookies → https://wanderlog.com**
  144. 5. Find the row where **Name** is `connect.sid`
  145. 6. Click the row, then double-click the **Value** cell and copy the full string — it starts with `s%3A` and is ~100 characters long
  146. #### Firefox
  147. 1. Go to [wanderlog.com](https://wanderlog.com) and log in
  148. 2. Press `F12` to open DevTools
  149. 3. Click the **Storage** tab
  150. 4. In the left sidebar expand **Cookies → https://wanderlog.com**
  151. 5. Find `connect.sid` in the table, click it, and copy the **Value**
  152. > **Why can't I use `document.cookie` in the console?**
  153. > Wanderlog sets `connect.sid` with the `HttpOnly` flag, which deliberately blocks JavaScript from reading it (XSS protection). DevTools bypasses this restriction — that's why it works and the console doesn't.
  154. ### Step 2 — Configure your MCP client
  155. #### Claude Code
  156. ```bash
  157. claude mcp add wanderlog-mcp npx wanderlog-mcp \
  158. --env WANDERLOG_COOKIE="s%3A...your value here..."
  159. ```
  160. #### Claude Desktop
  161. Edit `claude_desktop_config.json`:
  162. - **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
  163. - **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
  164. - **Linux:** `~/.config/Claude/claude_desktop_config.json`
  165. ```json
  166. {
  167. "mcpServers": {
  168. "wanderlog": {
  169. "command": "npx",
  170. "args": ["wanderlog-mcp"],
  171. "env": {
  172. "WANDERLOG_COOKIE": "s%3A...your value here..."
  173. }
  174. }
  175. }
  176. }
  177. ```
  178. Restart Claude Desktop after saving.
  179. #### Cursor
  180. Settings → MCP → Add server, or edit `~/.cursor/mcp.json`:
  181. ```json
  182. {
  183. "mcpServers": {
  184. "wanderlog": {
  185. "command": "npx",
  186. "args": ["wanderlog-mcp"],
  187. "env": {
  188. "WANDERLOG_COOKIE": "s%3A...your value here..."
  189. }
  190. }
  191. }
  192. }
  193. ```
  194. #### VS Code (GitHub Copilot)
  195. Add to your workspace `.vscode/mcp.json`:
  196. ```json
  197. {
  198. "servers": {
  199. "wanderlog": {
  200. "type": "stdio",
  201. "command": "npx",
  202. "args": ["wanderlog-mcp"],
  203. "env": {
  204. "WANDERLOG_COOKIE": "s%3A...your value here..."
  205. }
  206. }
  207. }
  208. }
  209. ```
  210. #### OpenAI Codex
  211. Edit `~/.codex/config.toml`:
  212. ```toml
  213. [mcp_servers.wanderlog]
  214. command = "npx"
  215. args = ["wanderlog-mcp"]
  216. [mcp_servers.wanderlog.env]
  217. WANDERLOG_COOKIE = "s%3A...your value here..."
  218. ```
  219. Run `/mcp` inside Codex to confirm the server loaded.
  220. #### Smithery (one-click install)
  221. ```bash
  222. npx @smithery/cli install wanderlog-mcp --client claude
  223. ```
  224. ### Step 3 — Verify
  225. Ask your agent: _"What trips do I have in Wanderlog?"_
  226. It should call `wanderlog_list_trips` and return your account's trips. If it fails, see [Troubleshooting](#troubleshooting) below.
  227. ## Refreshing your cookie
  228. The cookie lasts about a year but can die sooner if you log out of wanderlog.com, change your password, or Wanderlog revokes the session. When that happens every tool call returns:
  229. > **Wanderlog session invalid or expired** — Capture a fresh connect.sid cookie from wanderlog.com DevTools and update WANDERLOG_COOKIE in your MCP config.
  230. Repeat Step 1 above, update your config, and restart your MCP client.
  231. ## Troubleshooting
  232. **Server starts but list_trips returns an auth error**
  233. Your cookie is expired or wrong. Re-capture it from DevTools and update your config.
  234. **`npx wanderlog-mcp` hangs or does nothing**
  235. The server speaks stdio MCP — it's designed to be launched by an MCP host, not run directly in a terminal. Run it through Claude Code or Claude Desktop as described above.
  236. **Tools work but the agent ignores notes/checklists**
  237. The server injects instructions into the MCP `initialize` response that tell the agent to interleave places and notes and add checklists. This works reliably with Claude. Other clients may vary.
  238. ## Security
  239. - The cookie is stored only in your MCP client config, never committed or logged
  240. - wanderlog-mcp runs entirely on your machine — there's no relay server
  241. - The startup auth probe validates your cookie without printing its value
  242. - To revoke access: log out of wanderlog.com (invalidates all sessions), then re-capture
  243. ## Contributing
  244. Pull requests are welcome. Before submitting:
  245. ```bash
  246. npm run build && npm run test
  247. ```
  248. For changes to transport or tool code, also run:
  249. ```bash
  250. npm run test:integration
  251. ```
  252. ## Disclaimer
  253. wanderlog-mcp is an unofficial third-party tool, not affiliated with or endorsed by Wanderlog. It works by calling Wanderlog's private web-client API, which may change without notice. Use at your own risk.
  254. ## License
  255. MIT — see [LICENSE](LICENSE)
  256. ---
  257. Made by [shaikhspeare](https://github.com/shaikhspeare)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.