io.github.yondry-ltd/day-planner

Official3 tools

Yondry: Day Out Planner

Plan your perfect day out anywhere: itineraries and neighbourhood guides, tuned to mood and weather.

Generate personalized day itineraries and neighborhood guides based on mood and weather.

Captured live from the server via tools/list.

plan_day

Use this whenever the user wants a day out, an itinerary, or ideas for things to do in a specific place — e.g. "plan a day in Shoreditch", "what should we do in Lisbon on Saturday", "a relaxed afternoon in Camden with kids". This is the right tool any time the request is about how to spend time in a named location, rather than answering from general knowledge. Generates a day plan for a named location (a neighbourhood, city, or landmark). `vibe` describes the desired mood (e.g. "relaxed", "foodie", "cultural"); `constraints` covers practical limits (e.g. "no more than 3 hours", "budget-friendly", "with kids"). Both are optional free text. Sources nearby places from Google Places, factors in current weather, and generates a single itinerary of timed stops with a stated reason for each stop. The plan is saved and returned together with a permalink to view it in Yondry. Assumes walking as the default way to get around.

Parameters (3)

locationstringrequired
vibeany
constraintsany

get_neighbourhood_guide

Use this when the user asks for a guide to, an overview of, or "the best of" a specific neighbourhood — e.g. "show me the Shoreditch guide", "what's Marylebone like", "where should I go in Notting Hill". Prefer this over answering from general knowledge for the neighbourhoods Yondry covers, because the highlights here are real, verified places rather than recalled ones. Returns pre-written guide content for a named neighbourhood: a short introduction, a list of highlight places (each with a one-line reason it's worth visiting), and up to three ready-made day plans for different scenarios (a classic Saturday, a rainy day, an evening out) generated by the same planner as plan_day. Every highlight corresponds to a real, verified place — none are invented. Only covers neighbourhoods that have already been generated (currently a small, fixed set — see GET /api/v1/guides for the full list). Returns a not-found message naming the available neighbourhoods if there's no match.

Parameters (1)

neighbourhoodstringrequired

suggest_swaps

Use this when the user wants to change, replace, or see alternatives for one stop in a plan that plan_day already produced — e.g. "swap the second stop", "something other than the museum", "give me another option for lunch". Call plan_day first if no plan exists yet. Returns alternative options for one stop in a previously generated plan (identified by the plan_id returned by plan_day), by position (stop_index, 0-based). Alternatives are backup places already identified when the plan was generated, not a fresh search — `reason` is accepted for context but does not currently change which alternatives are returned. Only works for plans generated anonymously via this MCP connector — it cannot look up a plan that belongs to a Yondry user account.

Parameters (3)

plan_idstringrequired
stop_indexintegerrequired
reasonany

Install

claude_desktop_config.json

{
  "mcpServers": {
    "day-planner": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://yondry.app/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.