wanderlog-mcp
Related Servers
Alternatives to wanderlog-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceCoordinates flights, hotels, events, weather, currency, and traffic data through a single MCP server, enabling comprehensive trip planning via natural language prompts.MIT
- FlicenseAqualityCmaintenanceMCP server for creating day-by-day trip itineraries in SQLite, with a planner agent that uses a Tavily search scout via tool boundaries. Enforces guard rails like rejecting activities on out-of-range days.3-
- AlicenseNot gradedqualityCmaintenanceMCP server for multi-agent travel planning, orchestrating parallel expert calls to generate structured itineraries and persist them to SQLite.MIT
- FlicenseNot gradedqualityBmaintenanceMulti-domain MCP server enabling AI agents to plan and execute vacation travel and birthday party logistics via local tool pipelines.-
- FlicenseNot gradedqualityDmaintenanceA Kyoto travel planning assistant that uses Wikivoyage API and LangChain/LangGraph to provide real-time attraction info, operating hours, and dynamic itinerary adjustments through MCP tools.-
- FlicenseNot gradedqualityDmaintenanceA proof-of-concept MCP server that allows LLM agents to query live flight booking information via Amadeus, including cheapest tickets, destinations, and airline routes.1-
TDQS
Scored across 18 tools
Most tools target distinct resources and actions (trips, places, notes, checklists, expenses, guides), so an agent can generally select correctly. The main overlap is between add_place's 'note' parameter, standalone add_note, and annotate_place, all of which can attach notes to an itinerary.
All tools share a consistent 'wanderlog_<verb>_<noun>' snake_case pattern with no style mixing. Verbs are predictable (list, get, search, create, add, edit, remove, update, rename), and resource names are consistent.
18 tools is on the heavier side, but each tool maps to a distinct itinerary-building action and none feel redundant. The count is slightly high but still reasonable for a travel-planning domain.
The set covers the core trip lifecycle well: create/list/get/populate, add places/hotels/notes/checklists/expenses, and edit/remove sub-items. Obvious minor gaps exist—no delete_trip, no dedicated flight/train creation, and no checklist/expense removal—but agents can work around most of these.