lesgooo

View saved version →

---
name: group-planning
description: Use lesgooo.fun to create or coordinate a shared group plan, read an existing plan link, collect availability, handle RSVPs and place votes, manage a checklist, or track shared expenses.
---

# Group planning with lesgooo

lesgooo.fun is a free group planner with no accounts. One shared plan link lets friends participate in a browser without this plugin. Its MCP server exposes 24 tools, including three app-only UI transport tools, for dates, places, RSVPs, checklists, and shared costs.

## Choose the plan

- If the user supplies a saved lesgooo plan link or a four-character plan ID, use `get_plan` to read it. A bare `/when`, `/where`, `/rsvp`, `/checklist`, or `/splitwise` URL starts a local draft; ask for the shared plan link instead.
- An explicit link or ID overrides older conversation and app context. A bare draft link must never fall back to a previous saved plan.
- When an action needs a new plan and no saved plan is selected (e.g. “add that I am free next weekend”), call `create_plan` once, then complete and verify the requested action using its returned organizer credentials. Use any title and name already explicitly supplied in this conversation. Omit missing fields; do not invent a person's name or infer an event title from the action. Omitted fields get temporary “Event” / “Organizer” labels. Return the relevant share link.
- **After the requested action succeeds**, report it briefly and ask in chat only for the `missing_details` returned by creation: name (`your_name`), event title (`title`), or both together in one question, in the user's language. Example: “Volné dny jsou uložené. Jak se jmenuješ a jak máme událost nazvat?” If both were supplied, ask neither. Free days are availability, not an agreed event date or an RSVP.
- On the user's answer, keep the original `plan_id` and credentials. To fill their name, call `join_plan` with `name` **and the original `participant_id` and `participant_token`**; this renames the same organizer and preserves their availability/RSVP/entries. To fill the event title, call `update_event` with `title` and those credentials. Read `get_plan` to verify. Never create another plan or participant, and never replay dates just to fill these details. If they provide only one detail, update it and ask only for the other missing one. If they skip, keep the saved action and do not repeatedly insist.
- If `create_plan` returns `participant_error`, the plan already exists. Keep its `plan_id` and call `join_plan`; never call `create_plan` again just to add the person.
- A plan link grants access to shared content. Don't send it to other people or services unless the user asks. Don't put secrets or sensitive personal details into plan fields.

## Act for one person

- `join_plan` returns `participant_id` and `participant_token`. Keep both in the current conversation for that plan and pass them to writes made as that person. Do not show the token in a reply or place it in a plan field.
- Credentials are scoped to the selected person **in that plan**. Reading or opening a plan does not require choosing a person. Before writing, use an explicit self-identification, credentials already selected in this conversation for the same plan, or an actually received explicit UI participant selection. Never infer identity from the sole participant, a mentioned friend/payer, a default “Organizer” label or “I am the organizer” without a name. There are no authenticated roles or special organizer privileges.
- If identity is unclear, read `get_plan` and ask one short question in the user's language with existing names and an option to join as new: “Jsi Jana, Petr, nebo se chceš přidat jako někdo nový? Jaké jméno mám použít?” Retain the requested action. After their answer, select/join and complete it; do not ask approval for that same clear action again. A generic “yes” or “I am new” without a name still needs clarification.
- Use `join_plan` **without participant credential

Preview of the first 4,000 characters. Read full instructions →