# Preflight > Preflight is TripIt for AI agents: one MCP connection for Trips, a shared ledger of bookings, travelers, dependencies and deadlines that checks the trip; Shop, orders from forwarded receipts; Todo, the person's todos; and Files, their documents. None of them books, buys, pays or contacts anyone. This file is https://preflight.generalledger.tech/llms.txt; the home page answers `Accept: text/markdown` with it. The MCP server is at https://preflight.generalledger.tech/api/mcp (Streamable HTTP). Sign-in is OAuth 2.1 with PKCE, and a client identifies itself with dynamic client registration or a client ID metadata document, so a client that follows the protocol's discovery needs nothing else: the first call without a token answers 401 with the discovery address (https://preflight.generalledger.tech/.well-known/oauth-protected-resource, then https://preflight.generalledger.tech/.well-known/oauth-authorization-server). There is no API key and no separate REST API. Anyone with a verified Google address can sign up; a trip invitation sent to that address is accepted in Settings. Before connecting, https://preflight.generalledger.tech/api/mcp/server-card is the MCP server card (name, version, the remote; also at /.well-known/mcp-server-card) and /sitemap.xml lists the public pages. Connect an agent: - Claude (claude.ai, desktop and mobile): Settings → Connectors → Add custom connector, with the server URL https://preflight.generalledger.tech/api/mcp. Then sign in with Google and approve. - Claude Code: `claude mcp add --transport http --scope user preflight https://preflight.generalledger.tech/api/mcp`, then run `/mcp` to sign in. - Any other MCP client that supports remote servers with OAuth: give it the server URL and follow its sign-in. - Once connected, start each product with its read: `todo { since: "last" }`, `shop {}`, `files {}`, and for trips `trip { since: "last" }`. On trips, a genuinely new agent receives current open questions and claims, an explicit event baseline and full-replay guidance; earlier event history is outside that initial selection. Later calls deliver changes page by page and advance only the read cursor. `trip { since: 0 }` requests full replay without consuming either cursor; follow its numeric continuation hint. `trip { digest: true }` summarizes changes using a separate digest cursor and never drains `since`. SOURCE MAIL: forward, don't retype. To add a booking, receipt, refund or change from the person's mail, forward the original email inline from their own address to the forward_to address that trip { inbox: true } returns (a Gmail connector's forward does this), then read the result in trip { inbox } and record only what the email can't know: attendance, decisions, corrections. Restating the email's facts with booking.upsert or money.upsert makes a second, weaker copy of the same mail. Retype only facts with no email behind them (a phone call, a vendor page). The tools, by product: Trips has `trip` to read (upcoming trips, a trip day by day, checks, deadlines, what changed), `trip_record` to write the ledger and the notes shared between people and agents (facts, decisions, questions, claims, handoffs), and `trip_show` to show a trip as a card in the chat. Shop has `shop` and `shop_record` for online orders and receipts (account owners). Todo has `todo` and `todo_record` for the person's own todos. Files has `files` and `files_record` for their own documents (text read on the server, five-minute upload and download links). Every writer takes `{ ops: [...] }`. `feedback`, for any product, tells the people who build the tools what was missing, broken or confusing. ## Docs - [Everything in one file](https://preflight.generalledger.tech/llms-full.txt): what the server tells every agent on connect, each tool's rules, how to connect, and every tool parameter, generated from the schemas the server registers (89 KB)