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 manage trips and tasks, show your Preflight, track expenses, work with booking documents, catch up on crew chat and help with group decisions. Compatible clients also display interactive trip cards.

Visit Limbo MCP for a copyable connector address, setup steps for your assistant, and the complete example prompt library. Already connected? Jump to the examples. The same page is available at Connectors, also linked under Connect in the website footer. For Muse, see the separate early-access status and setup notes.

Example prompt library

Search by what you want to do or choose a category. These examples cover the currently available workflows, from reading a trip to editing a task, recording a repayment or opening an interactive card. Prompts that save a reviewed preview are follow-ups: first create and review that preview in the same conversation.

New to the connector? Follow the setup steps below. The detailed sections explain permissions, limits and what each action changes.

What you need

• An existing Limbo account. All available connector tools are free.
• 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 apply separately from Limbo.
• 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 are included when available. Ask “Show me the Google place photo for Marble Mountains” to load a fresh picture of a plan’s linked place, with source and photographer credit. Your chat provider may show images inline or as links. Missing photos are left out, and illustrative images are labelled. The trip and plan read tools omit booking credentials, private contact details and attachment download links. Opening a booking document uses the separate document permission.

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 preview includes the plan’s category and subtype. Meals use Activity → Food; beaches, temples, and museums use Activity → Activity. Stays use Accommodation → Hotel, Airbnb, or Other. Transport uses Private, Car rental, Train, Bus, or Ferry. Tell your assistant the purpose of a plan when a place supports more than one activity—for example, dinner at a hotel is a food plan. You can correct a subtype later without replacing the plan. Converting between flight, cruise, transport, and other forms still uses the app.

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. If saving is retried, Limbo avoids adding the same plans twice.

Create or edit a trip

You can create a trip before you have an itinerary:

Create a Da Nang trip for 14–20 September 2027, using Vietnam local time.

To change a trip, name it and specify the fields to update:

Set my Da Nang trip’s dates to 14–21 September 2027.

You can change its name, destination, description, dates, timezone, and currency. Review the change before saving. If more than one trip has the same name, choose the right one first. Normal editing permissions and date rules apply. Changing trip dates does not shift the dates of plans already in the trip.

Edit a plan

Ask your assistant to find the exact plan, then describe and approve your changes. For example:

Move Hoi An Old Town in my Da Nang trip to 2 pm on 17 September 2026. Keep the existing plan and its end time.

The plan keeps its ID, votes, comments, and attachments. You can change its name, description, notes, start and end times, timezone, venue/address, budget, and supported plan category or subtype. Only the fields you request change. A venue change refreshes its map identity. If the new start is after the old end, also specify the new end time.

Refresh the connector’s tool list or reconnect if your assistant still suggests deleting and recreating a plan to edit it.

Remove plans

Ask your assistant to show the plans you want to remove, then approve the exact selection. For example:

Remove the Marble Mountains plan from my Da Nang trip.

You need editing permission for the trip. Removal is permanent and also cleans up the removed plans’ attachments and flight monitoring. Check the selection carefully before approving.

Manage tasks and groups

Create, list, edit, complete, or remove real Checklist tasks from your conversation. They appear in the same trip Checklist as tasks added in the app.

For example:

• “Add ‘Check travel documents’ and ‘Book flights’ as tasks in my Da Nang trip, grouped under Before departure.”
• “List every task in Da Nang, including completed tasks.”
• “What task groups do I have, and which tasks are assigned to me?”
• “Set ‘Book flights’ to be due on 10 September 2027 at 9 am Sydney time, and assign it to me.”
• “Link that task to the flight plan, then mark it done.”
• “Move ‘Check travel documents’ into the Documents group and update its notes.”
• “Remove the ‘Book flights’ task. Keep the flight plan.”

Each task belongs to a trip. Name the trip or select it from your trip list; if names match more than one trip, choose the correct one. Optional fields include notes, group, category, due date, crew assignment, a link to a plan in that trip, and list order. A due date does not schedule a reminder notification.

Groups are labels you choose, such as Documents or Packing. Adding a task to a new group creates that group; changing or clearing its group moves the task. A group disappears when it has no tasks. Categories match the app: Stay, Transport, Food, and Activity.

Unassigned tasks start up for grabs. Assigning an open task marks it claimed, and assigning someone else may notify them. Mark tasks done or reopen them without replacing the task. Clearing optional details removes only those details. Removing a task keeps its linked plan.

Trip permissions still apply. Everyone on the trip can read tasks and claim unassigned work for themselves. Assignees can complete or reopen their own tasks. Adding, editing, assigning others, and removing tasks require task management permission. These tools do not move an existing task between trips.

If your assistant offers to create note plans instead: refresh the connector’s tools or reconnect Limbo. Ask it to use the task tools. Existing connections with trip write permission can manage tasks; read-only connections need write permission to make changes.

Places and map details

When you create a trip or add plans, Limbo checks places in the background using Google Places. Verified locations receive map pins, timezones are filled in where available, and trip covers are added when available. The app uses those locations for its normal map and route views.

Open or refresh the trip after enrichment finishes. Temporary provider failures are retried. Vague activities and uncertain matches can remain unpinned; choose a more specific place when needed.

For a trip you imported earlier, ask:

Refresh the Google Places and map details for my Da Nang trip.

This checks the trip and its active plans without changing their names, dates, or votes. If your assistant cannot find these tools, refresh the connector’s tool list or reconnect Limbo.

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.
• A feature is unavailable: reconnect or refresh the tool list. Limbo does not require a subscription; your chat provider’s permissions and service availability still apply.
• 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. Trips you already saved remain in Limbo, and no Limbo subscription is required.

Get a trip briefing and update Preflight

Ask “What needs my attention for Lisbon?” to see upcoming plans, overdue Checklist tasks, pending votes and your personal Preflight. You can complete, reopen, dismiss or snooze your own Preflight items. Your preparation score and changes stay separate from the crew’s shared Checklist.

Use interactive trip cards

Ask “Show my Limbo trips” or “Show the Checklist for Lisbon.” In a client that supports MCP Apps, trip cards show available cover photos, destinations and dates. Open a trip to browse its itinerary, Checklist or ballots.

• Check a task to complete it. Uncheck your completed task to reopen it.
• Crew members can claim an unassigned open task, then complete their own work. Organizers and editors can manage the list.
• Choose Yes, No or Abstain, then press Cast vote. A choice in the selector is not saved until you press the button.
• Navigate to the next page when a list has more results.

Each action saves to the same trip you use in the app. If a save fails, the card keeps the previous state and shows an error. An uncertain connection can mean the save completed before the reply was lost; refresh the trip view before retrying. Your chat client may also ask you to approve an action.

Card availability depends on your client’s MCP Apps support. If a card does not appear, you can still ask for the itinerary, tasks or votes in text and request the same actions in conversation.

Track expenses and repayments

Ask to record an expense with its currency, who paid and how to split it. For example: “Record the $80 dinner I paid for in Lisbon and split it equally.” Review the amount and participants before saving. You can edit costs and splits, add payment records, see balances and record a repayment that has already happened.

Balances follow the app’s rules: only confirmed expenses with recorded payments contribute. Currency conversion needs available exchange rates. Recording a payment or repayment never charges a card or transfers money. See who owes whom.

Work with booking documents

With document permission, find confirmations by filename or plan name and ask to open a selected file. Viewing links expire after a few minutes; request a fresh link if needed.

To import a booking, upload its PDF and name the trip. Your assistant can read selectable text, extract the booking facts and show a preview of the proposed plans. Check dates, timezones, places, types and prices before approving the import. The original confirmation is attached to each imported plan, and places receive the same background enrichment as other new plans.

Scanned PDFs and images need a chat client that can interpret the image. You can also attach a PDF, JPEG, PNG or HEIC file directly to a trip or existing plan. Files are limited to 15 MB each and use the app’s attachment permissions and storage limits.

If an import reports that plans saved but a document upload failed, ask it to finish the same import. Retrying the same preview resumes attachment uploads without duplicating plans. An unused preview expires after 15 minutes. Importing a confirmation does not buy, cancel or change the booking with its provider.

Manage ballots and move plans together

Ask to create up to five separate sealed proposals, compare their details, or see revealed results. Proposing records your yes vote when voting opens. A draft waits until there are enough eligible voters. Organizers can change an open deadline or approve or reject a proposal; the trip owner can open a draft. Reopening a ballot discards the previous votes and requires your explicit approval.

To move several plans, ask for a preview: “Move Tuesday’s activities to Wednesday.” Review each before-and-after time, overlaps and any plans outside the trip dates. Approving the preview changes the existing plans together while keeping their votes, comments and attachments. If the trip changes before you approve, request a fresh preview. Moving by a fixed number of hours preserves elapsed time; check local times when a daylight-saving change is involved.

Changing a stored flight date does not change your airline ticket. Flight monitoring may need to be enabled again for the new date.

Catch up on chat and refresh a flight

With chat permission, ask what you missed in the trip’s recent messages. Reading through the connector does not mark those messages read in the app. You can ask for a draft reply; sending needs your explicit instruction for the exact text and recipient trip, and may notify the crew.

Ask to refresh an existing flight plan for the latest available status, times, gates and terminals. Provider availability and refresh limits apply. Refreshing a flight does not move the rest of your itinerary automatically.

Reuse task lists and restore work

Create several tasks at once, including their groups, due dates, assignees and links to plans in the selected trip. You can apply the built-in Packing, Documents and Pre-departure templates, or save a personal template for future trips. Reusable templates keep task titles, notes, categories and groups; add trip-specific dates, people and plan links separately.

Ask to rename a group to move all its active tasks to that label. Renaming to an existing group combines the groups. Removed tasks can be listed and restored with their saved notes, group and completion state; links to removed plans and assignees who left the trip are cleared.

A large task batch can stop partway through if a task cannot be saved. Ask to retry the same batch to finish it without duplicating earlier tasks.

Enable the expanded tools

Refresh Limbo’s tool list or reconnect. Approve the additional chat and document permissions if you want those workflows; a connection with only trip and voting permission cannot read chat or open documents. Your trip role and connection permissions are checked for every action. MCP actions require an internet connection.