Set up Wanderlog MCP for Cursor and Claude
Wanderlog MCP connects coding agents to Wanderlog through the Model Context Protocol. Copy the install command from the Wanderlog MCP listing—that page owns auth notes, compatible clients, and the source link.
Use this guide after you open the listing: register the server in Cursor or Claude, then verify with a read-only tool call. If you searched for wanderlog mcp, the listing is canonical; this post is the HowTo spoke.
What Wanderlog MCP is
Wanderlog MCP is an MCP server (tools and live access), not an agent skill. Confirm transport, tool list, and whether an account or API key is required on the live page before you store secrets in a client config.
Install command
Copy the command shown on Wanderlog MCP. Do not substitute a guessed npm package. Re-check the listing if upstream renamed the server or changed stdio vs HTTP.
Client setup
- Open MCP settings in Cursor, Claude, VS Code, or Codex.
- Add a server entry with the listing command and any required env vars.
- Restart MCP and ask the agent to list Wanderlog tools.
- Run one read-only action against a test trip or dataset you control.
Caveats
- Use a dedicated account or test data. Do not point write tools at production itineraries until you have seen the tool list.
- Client support differs. Bowora documents Cursor, Claude, VS Code, and Codex on MCP clients.
When to choose something else
Design files: Figma MCP Bridge setup. General servers: the MCP servers list. Figwright: Figwright MCP setup.
Related: Wanderlog MCP listing, Figwright MCP setup, MCP clients, and the MCP servers list.
FAQ
- Where is the Wanderlog MCP install command?
- Copy it from /mcp/wanderlog-mcp. Do not guess a package name.
- Does Wanderlog MCP need an API key?
- Follow the listing. If auth is required, use a scoped or test credential.
- Which clients does Bowora document?
- Cursor, Claude, VS Code, and Codex.
- Where is the source?
- Linked from /mcp/wanderlog-mcp.
