The short version
- The connector is a Model Context Protocol (MCP) server at
https://api.tripami.io/mcp. It uses Streamable HTTP, and you sign in with OAuth. - It acts as you. It sees only the trips you're on, and it can do only what you can do in the app.
- Tripami gets only what the assistant sends when it uses a tool, never your conversation.
- Removals, money and other sensitive changes wait until you approve them in Tripami. The assistant can't approve them for you.
- It never books travel, moves money or sends messages.
- You can disconnect anytime, in the assistant or in Tripami.
1. What Tripami does
Tripami is a shared live trip app for friends. A trip holds everyone's plans, stops, bookings, notes and shared expenses in one place, so the whole group knows what's next, even when people split up to do different things.
The connector brings that trip into your AI assistant. You can plan in ChatGPT or Claude, then ask it to save the plans you keep: “Add the pasta-making class to our Italy trip, Thursday at 7:30.” You can also ask about the trip, like “What's missing from our Florence day?” or “Who still owes for dinner?”, and the assistant answers from what's actually in Tripami.
2. Connect an assistant
Add Tripami as a custom connector with this address:
https://api.tripami.io/mcp
Claude
- In Claude, open Settings, then Connectors, and choose Add custom connector.
- Name it Tripami and paste the address above.
- Choose Connect, then sign in to Tripami and approve when asked.
ChatGPT
- In ChatGPT, open Settings, then Apps & Connectors. Under Advanced, turn on Developer mode, then choose Create.
- Name it Tripami, paste the address above and choose OAuth.
- Sign in to Tripami and approve when asked.
Tripami isn't listed in either assistant's connector directory yet, so it's added by address for now. Support for Muse by Meta is coming. The Tripami app shows these steps too, under Profile, then Connectors.
3. How sign-in works
When you connect, the assistant opens a Tripami page in your browser:
- You sign in to your Tripami account with Apple, Google, or email and password. If you don't have an account yet, you can create one there. Phone-number sign-in isn't available on this page yet.
- Tripami shows which assistant is asking and the permissions it wants, in plain language.
- You choose Allow or Deny. You approve or decline the whole set of permissions the assistant asked for.
Your assistant is connected to the same Tripami account you use in the app, so it sees the same trips. Tripami never matches accounts by email address.
For developers
- Flow: OAuth 2.1 authorization code with PKCE (S256 only). There are no client secrets; every client is a public client.
- Discovery:
https://api.tripami.io/.well-known/oauth-protected-resourceandhttps://api.tripami.io/.well-known/oauth-authorization-server. Requests without a valid token get a standard OAuth challenge. - Endpoints:
/oauth/authorize,/oauth/token,/oauth/revokeand/oauth/register, all onhttps://api.tripami.io. - Client registration: ChatGPT and Claude register themselves (dynamic client registration, RFC 7591). Every redirect address must be HTTPS on that assistant's own site:
chatgpt.comorchat.openai.comfor ChatGPT, andclaude.aiorclaude.comfor Claude. Other clients can't register themselves. - Resource: tokens are issued for
https://api.tripami.io/mcponly, and redirect addresses must match exactly. - Tokens: sign-in codes work once. Access tokens last 15 minutes. Refresh tokens last 30 days and change every time they're used; reusing an old one ends the connection. A sign-in page left open expires after 10 minutes.
- Storage: Tripami keeps only hashes of tokens, and they're separate from the Tripami app's own sign-in.
- Scopes: if the assistant asks for none, it's asked for all of them. See Permissions.
4. Permissions
Each permission (OAuth scope) covers one kind of trip information. Tools check them separately, so an assistant without, say, the expenses permission gets no expense information, and Tripami tells it that the data was left out rather than empty.
| Scope | What it allows |
|---|---|
trip.read | Read your trip names, dates and destinations. Needed by every trip tool. |
trip.write | Create trips and propose changes to trip details. |
itinerary.read | Read plans, stops, timing, places and who's going. |
itinerary.write | Add plans, set your own attendance, add notes, and propose plan and stop changes. |
travelers.read | Read who's on the trip, their roles and preferences they chose to share. |
travelers.write | Add invited travelers and update shared traveler details. |
reservations.read | Read shared booking details. |
reservations.write | Record bookings and propose booking changes. |
expenses.read | Read expenses and recorded balances. |
expenses.write | Propose expenses, splits and recorded payments, and save receipt details. |
intelligence.read | Read goals, decisions, shared memory and trip analysis, like free time and open questions. |
intelligence.write | Save shared memory, decisions and monitoring requests. |
trips:read, trips:write, trips:invite | Used by the original seven tools: read trips, create trips and add plans, and create invitation links. They don't give access to expenses, memory or the newer tools. |
5. What it can see
With the matching permission
- The trips you're a member of: their names, dates, destinations, goals and preferences.
- Plans and stops: what, when, where and who's going, including plans that don't have a time yet.
- The travelers on those trips: names, roles and preferences they chose to share.
- Shared booking details, and notes travelers added to plans.
- Expenses, splits and balances.
- Decisions, things the group asked Tripami to remember, and what still needs doing.
Never
- Trips you're not on. Tripami checks your membership on every request, and an ID alone never grants access.
- Your conversation with the assistant.
- Confirmation numbers, private booking references, or the booking links saved on plans.
- Other travelers' email addresses, phone numbers or account details.
- Your Gmail, your location, or your sign-in details.
Whatever the assistant reads from your trip is also handled under that assistant's own privacy policy. See the Tripami Privacy Policy for how Tripami handles information from AI assistants.
6. What it can change
The assistant should change your trip only when you ask. What happens next depends on the change.
Applied right away
- Creating a trip. Other travelers are added as invited, never as already joined.
- Adding a plan, or editing one that isn't confirmed. A plan without a time is saved to the trip without being scheduled.
- Your own attendance on a plan, and your own notes on plans.
- Adding an invited traveler, and updating shared traveler details: your own, or anyone's if you're an organizer.
- Recording a booking that isn't confirmed.
- Saving something the group asked Tripami to remember, and recording decisions.
- Saving receipt details for someone to check in the app. This doesn't create an expense.
- Creating invitation links, which the assistant gives back to you to share.
Waits for your approval
- Changing trip details, or archiving a trip.
- Removing anything: a plan, a traveler, a booking, a note, or something the group asked Tripami to remember.
- Changes to confirmed plans and confirmed bookings.
- Every expense, split, payment record and settle-up.
- Every change to stops, including moving a traveler.
For these, Tripami makes nothing happen yet. It sends the assistant a link to a review page that shows the change, before and after. You open it, sign in, and approve or decline. The link works for 10 minutes and only for the person who asked. It needs a recent sign-in, and it's refused if the item changed in the meantime. There's no way for an assistant to approve a change itself.
Same rules as the app
- Only organizers can manage travelers and stops. Travelers can move themselves between stops.
- The trip's owner can't be removed.
- An expense can be removed only by whoever paid, whoever added it, or an organizer.
- Every change records who made it and that it came from the assistant.
7. Tools
The connector has 67 tools, plus one the Tripami view uses to draw its map. Reading tools are marked read-only, so assistants can tell them apart from tools that change a trip.
Read only reads. Applies changes the trip right away. Review waits for your approval.
| Tool | What it does | Scope | Effect |
|---|---|---|---|
tripami.list_trips | List or search the trips you're on. | trip.read | Read |
tripami.get_trip | A trip's overview, with the details your permissions allow. | trip.read | Read |
tripami.get_trip_context | Goals, people, schedule, money, decisions, memory and upcoming actions, each filtered by permission. | trip.read, intelligence.read | Read |
tripami.create_trip | Create a shared trip from real dates, time zone and traveler count. | trip.write, travelers.write | Applies |
tripami.update_trip | Change dates, destinations, description, goals, preferences or budget. | trip.write | Review |
tripami.archive_trip | Archive a trip and keep its history. Organizers only. | trip.write | Review |
tripami.delete_trip | Permanently delete a trip for everyone on it, with its plans, travelers, expenses and photos. Owner only, and it can't be undone. | trip.write | Review |
tripami.connection_status | Which Tripami account is connected, and the permissions it has. | None | Read |
| Tool | What it does | Scope | Effect |
|---|---|---|---|
tripami.get_itinerary | Days, plans, places, times and who's going. | itinerary.read | Read |
tripami.add_itinerary_item | Save a plan. Without a time, it's saved unscheduled. | itinerary.write | Applies Review if confirmed |
tripami.update_itinerary_item | Change a plan. | itinerary.write | Applies Review if confirmed |
tripami.remove_itinerary_item | Remove a plan. | itinerary.write | Review |
tripami.update_attendance | Set your own answer for a plan: going, maybe or not going. | itinerary.write | Applies |
tripami.note_plan | Add or edit your note on a plan, like a stay's Wi-Fi code. Everyone on the trip sees it. | itinerary.write | Applies Review to remove |
tripami.add_stop | Add a stop: a city, its dates and who's there. Organizers only. | itinerary.write | Review |
tripami.update_stop | Change a stop's place, dates or who's there. Organizers only. | itinerary.write | Review |
tripami.remove_stop | Remove a stop. Organizers only. | itinerary.write | Review |
tripami.move_traveler | Move a traveler to another stop, so nobody is in two places at once. | itinerary.write | Review |
tripami.find_itinerary_gaps | Find clashes, free time, missing details and open questions. | intelligence.read | Read |
tripami.optimize_itinerary | Suggest timing and coordination fixes. It never reorders plans. | intelligence.read | Read |
| Tool | What it does | Scope | Effect |
|---|---|---|---|
tripami.list_travelers | Who's on the trip, their roles and shared preferences. | travelers.read | Read |
tripami.add_traveler | Add an invited traveler. It doesn't send them anything. | travelers.write | Applies |
tripami.update_traveler | Change a traveler's name or shared preferences: your own, or anyone's if you're an organizer. | travelers.write | Applies |
tripami.remove_traveler | Remove a traveler and their access. Organizers only; the owner can't be removed. | travelers.write | Review |
| Tool | What it does | Scope | Effect |
|---|---|---|---|
tripami.get_reservations | Shared booking details, without confirmation numbers. | reservations.read | Read |
tripami.add_reservation | Record a booking you already have. It doesn't book anything. | reservations.write | Applies Review if confirmed |
tripami.update_reservation | Change a recorded booking. It doesn't change the real booking. | reservations.write | Applies Review if confirmed |
tripami.remove_reservation | Remove a recorded booking. It doesn't cancel the real one. | reservations.write | Review |
| Tool | What it does | Scope | Effect |
|---|---|---|---|
tripami.get_expenses | Expenses and balances, kept separate by currency. | expenses.read | Read |
tripami.add_expense | Add an expense, optionally with its receipt lines, tax and tip. | expenses.write | Review |
tripami.update_expense | Correct an expense. | expenses.write | Review |
tripami.remove_expense | Delete an expense. | expenses.write | Review |
tripami.split_expense | Split an expense equally, by percentage or by exact amounts. | expenses.write | Review |
tripami.start_payment | Record that a payment was requested or started in a payment app. | expenses.write | Review |
tripami.update_payment | Mark a started payment as completed or cancelled. | expenses.write | Review |
tripami.settle_expense | Record a payment someone already made. | expenses.write | Review |
tripami.import_receipt | Save receipt details the assistant was given, for someone to check in the app. It doesn't create an expense. | expenses.write | Applies |
tripami.match_receipt_to_trip | Suggest which of your trips a receipt belongs to, by its date. | trip.read, expenses.read | Read |
| Tool | What it does | Scope | Effect |
|---|---|---|---|
tripami.answer_trip_question | Give the assistant the trip facts it needs to answer a question. | trip.read, intelligence.read | Read |
tripami.get_upcoming_actions | Open decisions, bookings still needed, attendance to confirm and unpaid shares. | intelligence.read | Read |
tripami.generate_trip_summary | A day-by-day summary of plans, travelers and expenses. | intelligence.read | Read |
tripami.generate_recommendations | Suggest next planning steps from what's already in the trip. | intelligence.read | Read |
tripami.remember_trip | Remember something the group said, like a preference or a constraint. | intelligence.write | Applies |
tripami.forget_memory | Forget something Tripami was asked to remember. | intelligence.write | Review |
tripami.record_decision | Record a decision, or a choice still to make, with its options. | intelligence.write | Applies |
tripami.update_decision | Update a decision or choose one of its options. | intelligence.write | Applies |
tripami.create_trip_monitor | Watch a flight for delays, cancellations and gate changes, and tell the travelers on it. Other kinds of watch are saved but not checked yet. | intelligence.write | Applies |
tripami.get_alerts | Read alerts saved on the trip. | intelligence.read | Read |
| Tool | What it does | Scope | Effect |
|---|---|---|---|
tripami.discover_places | Find real restaurants, sights and things to do near where the group will be, from Google, checked against the time, the budget, the group's size and what people like, with why each fits. | trip.read | Read |
tripami.update_shortlist | Add a place to the trip's shared shortlist, or take it off. | itinerary.write | Applies |
tripami.create_poll | Start a group vote, with options, who can vote, the rule and an optional deadline. | intelligence.write | Applies |
tripami.vote_poll | Cast or change your own vote. | intelligence.write | Applies |
tripami.get_poll | A poll's votes, who hasn't voted, and what's leading or decided. | intelligence.read | Read |
tripami.update_poll | Comment on a poll, suggest another option, or close it. | intelligence.write | Applies |
tripami.get_group_feed | What's changed on the trip, who did it and when. | trip.read | Read |
| Tool | What it does | Scope | Effect |
|---|---|---|---|
tripami.get_travel_options | Compare public transport, walking and a ride between two places on the trip, for the group's size, bags and preference. Nothing is booked. | trip.read, itinerary.read | Read |
tripami.get_trip_impact | What a flight's delay, cancellation or new times do to the group's later plans, and what to change or decide. Flights only. | trip.read, itinerary.read | Read |
tripami.report_disruption | Record a flight disruption that happened, so the group sees it and the travelers it affects are told. | intelligence.write | Applies |
tripami.resolve_alert | Mark a trip alert as handled. | intelligence.write | Applies |
tripami.get_flight_status | A flight's live status from AeroDataBox, from about 12 hours before departure. | trip.read, itinerary.read | Read |
| Tool | What it does | Scope | Effect |
|---|---|---|---|
create_shared_trip | Create a trip, with any plans it already has. | trips:write | Applies |
add_to_trip | Add plans, stays, transport, bookings or notes. | trips:write | Applies |
import_booking | Save a booking's known details. Incomplete ones stay unscheduled. | trips:write | Applies |
get_trip | Read a trip's shared details. | trips:read | Read |
find_trips | Find your trips by name. | trips:read | Read |
get_trip_gaps | Find a trip's gaps, like tripami.find_itinerary_gaps. | trips:read, intelligence.read | Read |
invite_travelers | Create invitation links for invited travelers. Organizers only. It doesn't send them. | trips:invite | Applies |
Every tool returns structured JSON and a text version. Anything Tripami doesn't know is left out rather than guessed.
8. Limits and rules
What it doesn't do
- It doesn't book, change or cancel real travel. Bookings in Tripami are records of ones you already have, and travel options link out to book elsewhere.
- It doesn't move money. Payments and settle-ups record what people say they paid in their own payment apps.
- It doesn't send messages. Invitation links go back to you to share.
- It watches flights only. Trains, ferries and weather aren't checked live; a request to watch them is saved, marked as waiting for a data source.
- Place search uses Google's ratings and regular opening hours. It doesn't check live availability, holiday hours or exact prices, and it never makes a reservation.
- It doesn't know ride, flight, rental car or transfer prices. Public transport times come from published schedules.
- It doesn't read your email, calendar or photos, and it doesn't read text from images. Receipt details have to come from the assistant.
- It doesn't reorder your plans, or fill in times, bookings or names nobody gave it.
Technical limits
- Up to 120 requests a minute from one IP address. Requests can be up to 256 KB.
- Trip context covers up to 500 records of each kind. For a larger trip, the request fails instead of returning part of it.
- Every change needs an idempotency key, so a retried request never makes a duplicate. Reusing a key with different details is refused. Edits and removals need the item's current revision.
- Money uses whole minor units, like cents, and each currency is kept separate. Nothing is converted.
- Text that arrives from bookings, receipts or other sources is treated as data, never as instructions.
Assistants
- ChatGPT and Claude can connect by address today. Muse by Meta is coming.
- Other MCP clients can't register yet. If you're building one, email support@tripami.io.
Using the connector
The connector is part of Tripami, so the Terms of Service and Privacy Policy apply to it. Use it only with your own Tripami account and the trips you're on, and don't use it to overload, probe or scrape the service.
9. Disconnecting and your data
- Disconnect in the assistant's connector settings, or on Tripami's Connected accounts page, where you sign in and choose Disconnect. The assistant's access ends right away.
- Plans and other changes it already made stay on the trip, like anything else you added.
- Tripami's request logs record the time, route and result of each request, not what was sent or any tokens.
- Deleting your Tripami account also ends every assistant connection. See Delete your account.
10. Help
Questions or problems connecting: support@tripami.io. Security issues: security@tripami.io, or see reporting a security issue.
Tripami is operated by Mythfit Corporation, 17814 N. 35th St., Phoenix, AZ 85032, USA.