Plan with friends using lesgooo and Grok Bot

lesgooo keeps the useful parts of a group plan together: When for availability, Where for places and votes, Event for agreed details and attendance, Checklist for tasks, and Splitwise for shared costs. A connected assistant can save supported changes instead of leaving you with a suggested itinerary to copy manually.

The Grok Bot package combines instructions for these workflows with the existing remote MCP server. MCP is the tool connection; the skill explains how to use it, choose the correct participant and avoid confusing availability with an agreed Event. This is an independent lesgooo integration, not a product made by or endorsed by xAI or Cursor.

Publication is being prepared. A public Grok Bot marketplace listing and installation link are not confirmed yet. A source package or successful MCP response is not proof of marketplace approval. The complete skill-and-tools plugin was tested through a private account installation in Grok Bot on 24 October 2026, with saved results independently checked. Public marketplace installation remains unverified. This guide explains supported planning tasks; check the actual listing before assuming the plugin is available.

When lesgooo appears in your Grok Bot catalog, use Connect apps to find and add it, then attach it to the conversation with @. The assistant host has its own account requirements and usage limits; no lesgooo account or API key is needed. Follow Grok Bot’s current app setup documentation for host-specific controls.

If you already use a host with custom remote MCP connections, the lesgooo endpoint is https://lesgooo.fun/mcp, using Streamable HTTP with no authentication. A raw MCP connection and installing the complete skill-and-tools plugin are different setup paths. See the MCP connection guide. You can always start directly on the web.

Tell the assistant your name, event title and intended timezone. For example:

“Use lesgooo to create a plan called Dinner with friends. I’m Alex. In Europe/Prague, add that I’m free on 14 November 2026 from 18:00 to 20:00, and all day on 15 November. Keep these as availability; we haven’t agreed on an Event date.”

In the planner, Days is for all-day responses and Days + Time is for specific hours. Ask “Which free hours actually overlap?” rather than assuming that two people available on Saturday can meet at the same time. The assistant should ask when the date, end time or timezone is unclear. Browser hours use the device’s local time.

If a new plan needs a temporary name or title, the assistant can complete a supported first action and ask for the missing details afterward. It should keep the same saved plan when you answer, rather than start another one. Read the visual guide to finding a time that works for everyone.

• Choose a venue: “Suggest Café Louvre on Národní in Prague and vote for it as me.” Matching Google Maps results are preferred; ambiguous venues need clarification. A manual place is an alternative when a suitable result is unavailable. No restaurant is booked.
• Make a real checklist: “Add Buy bread, Bring plates and Bring water as three separate checklist items.” Each task should have its own checkbox. Ask to mark a particular item done or update its text.
• Confirm the Event separately: “We agreed on 14 November 2026 at 18:00 in Europe/Prague. Save that as the Event date and RSVP yes for me.” This does not answer attendance for the other people.
• Track shared costs: “I paid 600 CZK for groceries. Split it equally between Alex, Sam and me.” Use names already in the plan and clarify the split if needed. Repayment entries record money already paid; lesgooo never moves money.

The same tools cover a dinner with friends, a group trip or a board-game night. Ask for a useful next step, not an automatic booking or invitation.

Paste the saved lesgooo link and identify yourself: “I’m the existing participant Alex. Add Sunday to my free days, keeping my other availability.” If you are joining, say “I’m new; add me as Sam.” Reading a plan needs no identity selection; writing an individual answer does.

If the assistant does not know who you are, it should ask whether you are an existing participant or someone new. Being the organizer or the only person in a plan does not establish identity. Choosing a name inside a visual planner may not pass that selection into chat on every host, so including the saved link and your name is the reliable fallback.

A bare /when or /checklist address is a local draft, not a shared plan link. Share it from the web first. The assistant cannot search every lesgooo plan or read another browser’s local drafts.

After saving, ask for the link and send it to your group yourself. Friends open it in a browser, select or add their name and participate. They do not need Grok Bot, the plugin or a lesgooo account.

Chat actions and the website use the same saved plan. Ask the assistant to read the latest state before relying on an older summary. It can summarize popular dates, actual common hours, suggested places, unfinished tasks and shared costs; a suggested settlement is not proof that money has been sent.

Anyone with a saved link can view and participate. Names are not authenticated identities, so keep secrets and sensitive information out of plan fields. Read the privacy policy and terms of use.

The web planner is the common interface and fallback. Displaying an interactive planner inside Grok Bot depends on host support for MCP Apps; a successful tool call alone does not establish that support. This guide does not promise the ChatGPT-style embedded UI in Grok Bot before it has been verified.

The plugin does not add automatic Google or Outlook calendar sync, background notifications, file imports, bookings or payments. It should report failed or partial actions honestly and preserve existing plan data. For the available tool behavior, see lesgooo MCP tools and example requests. For the separately published OpenAI integration, see the ChatGPT and Codex plugin guide.