Skip to main content
Connect to https://stardrift.ai/mcp to use these tools. The API reference documents the underlying HTTP operations; tool names and HTTP routes are not always the same. The API enforces authentication, permissions, and ownership. The MCP wrapper also validates inputs and filters place candidates.

Trips and itineraries

Day numbers start at 1 and must already exist. Use get_itinerary to inspect them. Use entry_id to edit, move, or remove a visit; item_id identifies its underlying activity. plan_version reports the current revision; it is not an optimistic-lock parameter.

Correct a visit

After adding a place, keep the returned entry_id. For example, move it from day one to day two:
Pass that object to move_entry. Then clear its annotation with update_entry:
The omitted time stays unchanged. Read get_itinerary afterward to verify the result.

Bookings and recorded events

There is no tool to add or edit a flight directly; forward its confirmation email to your import address. Event update/removal tools are not currently available. Recording an event does not buy a ticket.

Saved lists

A saved list is a collection of places, separate from a day-by-day trip. New MCP lists are private by default.

Edit an existing list in a fresh conversation

  1. Find the list by title with list_saved_lists.
  2. Call get_saved_list(list_id=…). Its list contains metadata and sections; items contains saved-item IDs. The default page size is 100, with a maximum of 200.
  3. Follow next_offset until null if you need every item.
  4. Use a saved item’s id for edits, removals, and section membership. Its place_id identifies the underlying place and is not the editing ID.
  5. Read the list again after edits. Removal tools may return no body.
Publishing requires an explicit visibility change. A populated public_url alone does not mean the list is public. After making a list private, anonymous reads return a private-list placeholder without its places.

Errors and recovery

Adding the same Google place again is not the name-collision error: the existing activity can be reused for another visit. Do not treat a 409 as proof that the requested place is already present. The tools preserve API error explanations. The wrapper can also return input errors such as Pass search_query or place_id, or No venue matched, without an HTTP status.