# RoundTrips

> Group trip planning. The RoundTrips MCP connector lets an AI assistant plan and coordinate a group trip on the user's RoundTrips account, and plan city time in walking order.

MCP endpoint, full connector (streamable HTTP, OAuth sign-in with RoundTrips): https://mcp.roundtrips.org/mcp
MCP endpoint, planning tools only (no sign-in): https://mcp.roundtrips.org/public
Setup and connector brief: https://roundtrips.org/connect/
OpenAPI (REST mirror of the no-sign-in planning tools): https://mcp.roundtrips.org/openapi.json

## Trip tools (signed in)
- my_trips: Answers: "Which trips am I planning?" Lists the signed-in user's RoundTrips trips with their role, who's in, and how far along each one is. No inputs. Example: {}
- trip_status: Answers: "Where does our trip stand, and what's still undecided?" Returns the trip's ideas with votes, the day-by-day plan, who's coming, recent comments, money owed, and a list of open questions. Ids in this answer are what the other tools take. Inputs: trip (name or id). Example: {"trip":"Lisbon"}
- start_trip: Answers: "Start a trip for us." Creates a RoundTrips trip owned by the user. Either pass plan (the save_plan object from day_itinerary, which brings every stop in as ideas already placed on their days), or from_zoe (a published trip slug such as "lisbon-without-the-checklist" to copy Zoe's trip), or just destination and days for an empty trip. Dates are optional. Inputs: destination, days (1–14), title, start_date (YYYY-MM-DD), plan, from_zoe. Example: {"destination":"Lisbon, Portugal","days":4}
- invite_link: Answers: "Give me a link to invite my friends." Returns the trip's join link to paste in the group chat. can_plan true (default) lets people add ideas, build days and log expenses; false lets them vote, comment and RSVP only. Organizers and co-planners only. Inputs: trip, can_plan. Example: {"trip":"Lisbon","can_plan":true}
- add_ideas: Answers: "Add these places to our trip." Adds 1–20 ideas to the trip's dream board for the group to vote on. Each idea: name (required), note, where, url, kind (museum, restaurant, viewpoint, …). Organizers and co-planners only. Inputs: trip, ideas. Example: {"trip":"Lisbon","ideas":[{"name":"Time Out Market","note":"Lunch on day one","kind":"market"}]}
- vote: Answers: "I'm in for that one." Adds (or with on=false removes) the user's vote on an idea. Everyone on the trip can vote. Inputs: idea_id (from trip_status), on (default true). Example: {"idea_id":"…","on":true}
- schedule: Answers: "Put that on day 2." Adds an idea (idea_id) or anything else (title) to a day of the trip, at the end of that day, optionally at a time. Organizers and co-planners only. Inputs: trip, day, idea_id or title, time (HH:MM), note. Example: {"trip":"Lisbon","day":2,"idea_id":"…","time":"10:00"}
- unschedule: Answers: "Take that off the plan." Removes one item from the day-by-day plan (the idea stays on the dream board). Organizers and co-planners only. Inputs: item_id (timeline id from trip_status). Example: {"item_id":"…"}
- rsvp: Answers: "Count me in." Sets the user's answer for a trip: in, maybe or out. Inputs: trip, answer. Example: {"trip":"Lisbon","answer":"in"}
- comment: Answers: "Tell the group…" Posts a message to the trip's comment thread, as the user. Only send words the user asked to send. Inputs: trip, message. Example: {"trip":"Lisbon","message":"Booked the tram tour for Tuesday"}
- add_expense: Answers: "I paid for dinner, split it." Logs an expense the user paid, split equally across everyone on the trip (the payer absorbs rounding). USD for now. Organizers and co-planners only. Inputs: trip, amount (dollars), description, category (stays, transport, food, activity, other), date (YYYY-MM-DD). Example: {"trip":"Lisbon","amount":84.5,"description":"Dinner at Taberna","category":"food"}
- settle_up: Answers: "Who owes who on this trip?" Works out the fewest payments that settle every shared cost. Inputs: trip. Example: {"trip":"Lisbon"}

## Planning tools (no sign-in)
- free_time_plan: Answers: "We're in this city with a few free hours, what do we do?" Returns 2–3 options, each a short route of stops in walking order with the walking minutes between them and a total that fits the hours. Inputs: city (required), hours (1–12, required), group (couple | friends | kids), vibe (e.g. "music", "food, views", "relaxed"), start_location (address, landmark or "lat,lng"; when given, the route starts there), when (morning | afternoon | evening | night or a time; evenings favour music and bars, daytime favours museums and parks). Stops from a published RoundTrips trip carry Zoe's own note; other stops come from open data (Wikidata, Wikipedia, OpenStreetMap) and are labelled that way. If coverage is thin the response says so. Example: {"city":"Nashville","hours":4,"group":"friends"}
- day_itinerary: Answers: "We have N days in this city, what should each day look like?" Plans each day with AI from the city's place data (Zoe's picks first where she has them) (a main sight or two, lunch, an evening idea, in time order), with every stop checked on the map and nothing scheduled on a day it is normally closed; cities RoundTrips doesn't cover get the same, clearly labelled as an AI suggestion. Pass start_date so closing days line up, and pass the traveller's own wishes in notes (e.g. "daytime only on the last day, don't over plan"). Every answer includes save_plan, ready for start_trip. related.trips lists Zoe's published trips for the city; offer one only if the user wants it (start_trip from_zoe copies it). Inputs: city (required), days (1–14, required), start_date (YYYY-MM-DD), group (couple | friends | kids), pace (relaxed | moderate | packed), vibe (interests), notes (free text). Example: {"city":"Madrid","days":4,"start_date":"2026-11-10","pace":"relaxed","notes":"daytime only on Friday"}
- whats_near: Answers: "What's worth walking to from right here?" Returns up to 10 places within the walking time, nearest first, each with walking minutes, a one-line reason or description, opening hours when known, and a directions link. Inputs: location (required: address, landmark or "lat,lng"), minutes_walk (1–45, default 15), type (e.g. food, coffee, bars, music, museum, park, views, kids, market, history). Example: {"location":"Ryman Auditorium, Nashville","minutes_walk":10,"type":"music"}
- list_cities: Answers: "Which cities can RoundTrips plan for, and how deep is the coverage?" Returns every covered city with its coverage level (curated = a published RoundTrips trip exists; open-map = OpenStreetMap places only; thin = few places) and place counts. No inputs. Example: {}

## Data
- Curated: places from published RoundTrips trips by Zoe (Lisbon, Tokyo, Amalfi Coast), with her notes.
- Open map: notable places from OpenStreetMap (ODbL) with Wikidata and Wikipedia descriptions, for about 50 cities.
- Walking times: OSRM foot routing over OpenStreetMap. Opening hours from OpenStreetMap where tagged.

## Pages
- Trips: https://roundtrips.org/explore
- Journal (written itineraries): https://roundtrips.org/journal/
- Privacy: https://roundtrips.org/privacy/