# Stardrift

> An MCP server for reading and editing your trips, itineraries, recorded bookings, and saved places.

MCP endpoint: https://stardrift.ai/mcp (Streamable HTTP with browser OAuth)
Scopes: guides:read, guides:write, bookings:read, saved:read, saved:write

## Docs

- [Connect Stardrift to Claude](https://docs.stardrift.ai/index.md): setup, permissions, sharing, and disconnecting
- [Tools](https://docs.stardrift.ai/tools.md): public tool catalog, editing IDs, pagination, null clearing, and errors
- [API reference](https://docs.stardrift.ai/api-reference/mcp-server/list-trips): generated HTTP operations available with public OAuth scopes

## Working with travel plans

- Use list_trips, then get_itinerary. Edit/move/remove a visit using entry_id, not item_id.
- move_entry preserves identity, time, and note without resolving the place again.
- update_entry preserves omitted fields; explicit null clears note/time. Use content to rewrite standalone notes.
- Use list_saved_lists, then get_saved_list. Follow next_offset until null. Use each saved item's id to edit it.
- Saved lists start private; trips start draft. Publish only on explicit request using update_saved_list or set_trip_visibility.
- record_stay, update_stay, remove_stay and record_event manage Stardrift records, not supplier purchases or cancellations.
- There is no direct flight-add tool or event update/removal tool. Flights can be imported by forwarding confirmation emails.
- The booking forwarding address is a private write-capable address; do not expose it.
- A 409 place-name conflict means the resolved place was not added; it is not a duplicate-success response.
- Paid lookups have a per-user daily cap, resetting at midnight UTC. Reads and moves do not resolve a new place.
- Private records are owner-scoped. Disconnect grants through Profile → Connected apps; revocation checks can take up to 60 seconds.