# 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 your AI assistant](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

## Connect a client

- [Claude](https://docs.stardrift.ai/clients/claude.md): claude.ai and Claude Desktop custom connector, Claude Code
- [ChatGPT](https://docs.stardrift.ai/clients/chatgpt.md): custom connector with developer mode
- [Cursor](https://docs.stardrift.ai/clients/cursor.md): install link and mcp.json
- [VS Code](https://docs.stardrift.ai/clients/vscode.md): install link, MCP: Add Server, .vscode/mcp.json
- [Codex](https://docs.stardrift.ai/clients/codex.md): codex mcp add and login
- [Gemini CLI](https://docs.stardrift.ai/clients/gemini-cli.md): gemini mcp add
- [Any MCP client](https://docs.stardrift.ai/clients/other.md): Streamable HTTP, OAuth discovery, 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.
- Created saved lists start private and trips start draft; lists imported from an Instagram or TikTok post start public, as in the app. 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 manual confirmed-flight recording 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.

## Search and plan

- search_flights returns one-way, round-trip, and multi-city cash options; search_hotels returns LiteAPI availability and room rates. No ranking subagents.
- get_search_results pages through owner-scoped results. References last 24 hours; rates are observations, not held inventory.
- add_search_result_to_itinerary saves an exact result as unbooked. Read journeys/stays with get_itinerary; remove with remove_search_result_from_itinerary.
- Users must visit the Stardrift website to book hotels. Give them the trip_url from saving their selection.