Plan with friends using lesgooo in Muse

Muse can already browse websites. The connector lets it work with lesgooo directly: it creates a saved plan, records each person’s availability, suggests and votes on places, sets the agreed Event, adds checklist items and records shared costs, and reads back exactly what was saved. No form filling, no screenshots and no guessing whether a click went through.

Because a plan is a link, the people you plan with do not need Muse, a lesgooo account or the connector. They open the link, pick their name and answer. Ask Muse later what changed and it reads the new answers.

• “Create a lesgooo plan called Cabin weekend. I’m Alex. Mark me free next Saturday and Sunday and give me the link to send to the group.”
• “Open https://lesgooo.fun/ab12/when and tell me which evening works for most people.”
• “I’m Alex in that plan. Add Café Louvre in Prague as a place and vote for it.”
• “I paid 1,200 CZK for groceries for all four of us. Record it in the plan.”
• “What changed in the plan since yesterday?”

• Endpoint: https://lesgooo.fun/mcp (MCP, Streamable HTTP, JSON-RPC 2.0).
• Authentication: none. A plan is a shareable link, like on the website. Changes need the participant_id and participant_token returned by create_plan or join_plan; the token is private to that person in that plan and is never shown in links or plan fields.
• Account, plan and region restrictions: none. lesgooo is free and works worldwide. Use is for people aged 13 or older (or the local minimum age) and ordinary group planning.
• Test access: no test account is needed. Create a fictional plan with create_plan and use the returned credentials.

Read tools change nothing. “Credentials” means participant_id and participant_token. Write tools change only the plan they are called on and only for the participant whose credentials are supplied. The one sensitive write permanently deletes data. No tool books anything, sends messages or moves money.

• get_plan (Read). Inputs: plan; time_zone, include_all_dates, since (optional). Returns: Title, Event, participants with all-day dates, exact time windows and RSVPs, best dates and shared free-time windows, places with votes, currency, server_time. With since: what changed after that time. Side effects: None.
• get_checklist (Read). Inputs: plan. Returns: Open and done items with item_id. Side effects: None.
• get_expenses (Read). Inputs: plan. Returns: Expenses, payments, balances and suggested settle-up transfers in the plan currency. Side effects: None.
• open_planner (Read). Inputs: plan, module, participant_id, participant_token (all optional). Returns: The plan view and its web links. Hosts without interactive views receive the links only. Side effects: None; opening saves nothing.
• create_plan (Write). Inputs: title, your_name, request_id (optional). Returns: Plan ID, share links for each module, participant_id and participant_token. Side effects: Creates a new plan and its first participant. Retrying with the same request_id returns the same plan.
• join_plan (Write). Inputs: plan, name; selection, existing_participant_id, participant_id, participant_token (optional). Returns: participant_id and participant_token. Side effects: Adds a participant or selects an existing one; with credentials, renames that participant.
• set_availability (Write). Inputs: plan, participant_id, participant_token, dates; time_slots, time_zone, mode (add, remove, replace). Returns: The participant’s saved availability. Side effects: Changes only that participant’s availability.
• set_rsvp (Write). Inputs: plan, credentials, status (yes, no, clear), occurrence_date (optional). Returns: The saved answer. Side effects: Changes only that participant’s RSVP.
• update_event (Write). Inputs: plan, credentials; title, start_date, start_time, end_date, end_time, location, description (each optional). Returns: The saved Event details. Side effects: Changes the shared Event everyone sees; omitted fields stay unchanged.
• add_place (Write). Inputs: plan, credentials, name; query, google_place_id, source (auto or manual), address, google_maps_url, link (optional). Returns: Up to five Google Places candidates (needs_selection, nothing saved) or the saved place with place_id. Side effects: Saves a place only after a candidate is chosen or source=manual; duplicates are merged.
• vote_place (Write). Inputs: plan, credentials, place_id, vote (up, down, clear). Returns: The place’s new score. Side effects: Changes only that participant’s vote.
• add_checklist_item (Write). Inputs: plan, credentials, text. Returns: The new item_id. Side effects: Adds one checklist item.
• check_item (Write). Inputs: plan, credentials, item_id, done. Returns: The item state. Side effects: Marks an item done or open again (reversible).
• add_expense (Write). Inputs: plan, credentials, description, amount; currency, paid_by_participant_id, split_among, allow_duplicate (optional). Returns: The saved expense and updated balances. Side effects: Records a cost split equally. Moves no money.
• record_payment (Write). Inputs: plan, credentials, to_participant_id; amount, allow_duplicate (optional). Returns: The saved repayment and updated balances. Side effects: Records a repayment that already happened. Moves no money.
• remove_entry (Sensitive write). Inputs: plan, credentials, kind, id. Returns: Confirmation of the deleted entry. Side effects: Permanently deletes an expense, payment, checklist item or place that this participant added. Cannot be undone.

• Every write returns the saved state, so the result is confirmed by the server rather than assumed. Read the plan again with get_plan, get_checklist or get_expenses before repeating a write.
• create_plan accepts a request_id; retrying with the same value returns the original plan instead of creating a duplicate. Availability, RSVP, votes and checklist state are idempotent, and add_expense and record_payment reject likely duplicates unless allow_duplicate is set.
• add_place with the default source returns needs_selection and up to five candidates without saving; the place is saved only when one candidate’s google_place_id is sent back.
• Invalid input, unknown participants, invalid credentials or ambiguous names return a tool error (isError: true) with a plain explanation, for example “Several people are called Alex. Use their participant_id from get_plan.” Nothing is saved when an error is returned.
• Draft links without a 4-character plan ID (such as https://lesgooo.fun/when) are rejected as targets for changes.

• 120 tool calls per hour per client.
• 20 new plans per day per client.
• Google Places lookups in add_place share the site’s monthly quota; when it is reached, places can still be saved with source=manual.
• When a limit is reached the tool returns an error saying when to try again.

lesgooo stores only what is saved into a plan: names as people enter them, availability, RSVPs, places and votes, checklist items, Event details and shared costs. It does not read your Muse conversations, email, contacts or calendar, and plan data is not used for advertising or model training. Anyone with a plan link can read that plan, so do not save passwords, payment-card details, government IDs, health information or data about children under 13. See the privacy and cookie policy and terms.

Questions or problems: lesgooofun@gmail.com. The full tool reference is on the Tools page.