Use Limbo with ChatGPT or Claude

Plan your trip in ChatGPT or Claude, then bring the itinerary into Limbo. Limbo's MCP connector is the connection between your chat assistant and your Limbo account. It can read your existing trips, plans, crew, and pending votes, add approved plans to a trip, cast your own explicitly chosen votes, and preview or save a new itinerary.

Visit Limbo MCP for a copyable connector address, setup steps for your assistant, and example trip prompts. You can also find MCP under Connect in the website footer.

What you need

• An existing Limbo account with active Limbo Pro, including when you only want to read trips or vote.
• Access to the email address you use for Limbo, to receive a sign-in code.
• A ChatGPT or Claude account that supports custom connectors and saving actions. Your chat subscription and workspace permissions are separate from Limbo Pro.
• An internet connection. Set up the connector in your chat provider, then open the saved trip in Limbo on your phone.

Connector address

Copy this complete address into your chat provider's MCP server URL field:

https://server.getlimbo.app/mcp

Choose OAuth if asked for an authentication method. Limbo uses email-code sign-in; you do not need to supply an API key or a client secret.

Connect with ChatGPT

1. Open ChatGPT on the web and enable Developer mode for an account or workspace with permission to create custom apps.
2. Open Settings → Apps → Create, or Workspace settings → Apps → Create for an administrator.
3. Name the app Limbo, enter the connector address above, and choose OAuth.
4. Select Scan Tools if shown. Complete Limbo's sign-in page with your Limbo email and the code sent to it, review the connection, then finish creating the app.
5. Start a new chat and select Limbo from the tools menu. Select or mention it again when a later message needs another Limbo action.

OpenAI currently documents full MCP saving actions for Business and Enterprise/Edu workspaces, with permission requirements. Its Pro plan has different custom-connector limits. If Create or saving actions are unavailable, check your workspace permissions and OpenAI's current setup guide.

Connect with Claude

1. Open Customize → Connectors and choose + → Add custom connector.
2. Name it Limbo and enter the connector address above. Leave optional OAuth client ID and client secret fields empty.
3. Add the connector, then choose Connect and complete Limbo's email-code sign-in.
4. Enable Limbo for your conversation from the + → Connectors menu.

On Team and Enterprise plans, an owner first adds the connector through Organization settings → Connectors. Each member then connects their own Limbo account. Menus and availability can change; see Claude's current connector guide.

Read your trips, plans, and crew

You can ask:

• “What trips do I have in Limbo?”
• “Show the full itinerary for Tokyo spring, including future plans.”
• “Who is coming on that trip?”
• “What plans do I have next week?”

The connector reads only trips you own or have joined. Ask explicitly to include archived trips. Long lists come in pages; your assistant can continue until it has all the results. Trip and plan dates include timezone information when available.

Trip covers and existing illustrative plan images are included when available. Your chat provider may show images inline or as links. Missing photos are left out, and illustrative images are labelled. Booking credentials, private contact details, and attachment download access are not shared by these tools.

Add plans to an existing trip

Name the trip and describe the addition, including the date and time. For example:

Add a museum visit on 3 April at 9 am Tokyo time to my “Tokyo spring” trip. Preview it before saving.

Review the trip and proposed plans, then approve the addition. If multiple trips share the same name, choose the right one first. You must have editing permission for the trip. Plans must fit its dates; the connector does not extend the trip automatically.

The trip's normal voting rules apply. A new proposal is sealed and proposing it records your yes vote. A trip without voting receives confirmed plans. Identical retries with the same request identifier return the original addition without creating duplicates.

Find proposals and vote in chat

Ask “Which proposals need my vote?” or limit the question to a named trip. Then choose a proposal and say, for example:

Vote yes on the crew dinner proposal in Tokyo spring.

The assistant can cast only your own vote, with an explicit choice of yes, no, or abstain. It cannot vote for another crew member. Deadlines, eligibility, and vote-change rules still apply. A final vote may resolve the proposal and notify the crew.

While a sealed ballot is pending, the connector shows participation and your own vote, but never the other voters' choices or running tallies.

Already connected? Refresh the connector's tools or reconnect Limbo and approve the separate voting permission. If you still see only the two original tools, remove and re-add the connector so your provider refreshes its tool list. An older connection cannot silently gain voting permission.

Preview, then save

Start with a small itinerary. For example:

Plan a three-day Melbourne trip for 12–14 December 2026. Include one activity each day. Use Limbo to preview the import, but do not save it yet.

Ask your assistant to use limbo_preview_trip_import. A successful preview checks the itinerary and returns its dates, counts, and any warnings. Previewing does not create a trip or change your saved plans. Make any corrections in the conversation and preview again.

When you are happy with the current plan, say:

Save this itinerary as a new trip in Limbo.

Your assistant uses limbo_import_trip. Review any action confirmation your chat provider displays. When saving succeeds, open the returned Limbo trip link while signed in to the same Limbo account. Check the dates and plans, then invite your crew.

You can ask for up to five activities to become sealed group-vote proposals. Other imported items become confirmed itinerary plans. There is no fixed trip-duration or day-count limit, although very large itineraries may need to be simplified.

If something goes wrong

• The connector cannot connect: check that the address ends in /mcp, choose OAuth, and confirm your provider allows custom connectors.
• Limbo asks for Pro: all connector tools require active Limbo Pro on the account you connected. A ChatGPT or Claude subscription does not include Limbo Pro.
• The sign-in code does not arrive: check the Limbo email address and your spam folder. Keep sign-in codes on Limbo's sign-in page, outside the chat.
• You see “Invalid or expired sign-in code”: return to your chat provider's connector settings, choose Connect again, and request a fresh code. Each code can be used only once. After selecting Connect Limbo, wait for the browser to return to your chat provider instead of submitting the code again.
• The preview reports a problem: ask your assistant to correct the reported dates, places, or activity details, then preview again.
• Saving times out: ask the assistant to retry the same import using the same idempotency key, the request's retry identifier. An identical retry returns the original trip rather than creating another one.
• The trip is missing: open the returned link and confirm the mobile app uses the same Limbo account you connected.

To stop using the connection, remove or disconnect Limbo in your chat provider's connector settings. If Limbo Pro expires, further previews and imports become unavailable. Trips you already saved remain in Limbo.