Limbo MCP for ChatGPT & Claude

It connects your chat assistant to your Limbo trips. Read trip details, existing and upcoming plans, crew, and pending votes. Add approved plans to a named trip, cast your own votes, or preview and save a new itinerary.

Yes. Active Limbo Pro is required for all connector tools, including reading trips and voting. Your ChatGPT or Claude plan is separate, and your provider must allow custom connectors and saving actions. Your crew can still join the saved trip and use Limbo's core planning features for free.

Your account needs permission to add a custom MCP connector. OpenAI currently documents full saving actions for Business and Enterprise/Edu workspaces. Claude supports custom remote connectors, with owner setup required for Team and Enterprise organizations. Check the setup guide for current provider requirements.

No. Connecting does not create a trip, and previewing does not change saved plans. Ask your assistant to save only after you have reviewed the current itinerary. Your chat provider may also display an action confirmation.

Yes. You can ask which proposals need your vote and vote yes, no, or abstain in chat. Each person can vote only for themselves. Vote changes and deadlines follow the trip’s rules, and pending sealed ballots hide other people’s choices.

Yes. Name the trip and describe the plans you want to add. Your assistant previews the addition before saving. If trips share the same name, choose the right one first. You need editing permission for that trip; adding a proposal also records your yes vote under the trip’s rules.

Available trip covers and saved illustrative plan images are returned with the details. Photos are optional, and illustrative images are labelled. Your chat provider controls whether images appear inline or as links.

Refresh the connector’s tools or reconnect Limbo. Approve the separate voting permission to cast votes. If your provider still shows only preview and import, remove and re-add the connector to refresh its tool list.

No. Add the connector URL, choose OAuth if asked, and sign in with the code sent to your Limbo email. You do not need a client secret. Enter your sign-in code on Limbo's sign-in page, outside the conversation.