Cursor + TripBooster

1. Add the TripBooster server URL to .cursor/mcp.json (see snippet below) or Cursor Settings → MCP.
2. When Cursor requests authentication, complete TripBooster browser sign-in and consent.
3. In Agent mode, ask to list_trips before import_email.
4. Settings → Developer in TripBooster documents OAuth and API key fallbacks.

https://tripbooster.dev/mcp

{
  "mcpServers": {
    "tripbooster": {
      "url": "https://tripbooster.dev/mcp"
    }
  }
}

OAuth sign-in is recommended. Developer API keys in Settings → Developer work for clients that cannot open the browser consent flow. Confirm with you before sync_gmail_reservations or import_email adds reservations to your vault.

• Ship and announce

  Turn release notes in your repo into validated multi-trip posts without leaving Cursor.

• Docs-driven threads

  Summarize a markdown doc into an X thread draft with list_pending_imports per placement.

• Blog + social

  Draft social teasers that link to posts you already imported through TripBooster.

• Inbox from IDE

  list_pending_imports for support-heavy launches; you send from TripBooster after review.

Agents read trips, reservations, wishes, alerts, and tasks. Mutating tools are limited to sync_gmail_reservations, import_email, and reviewing list_pending_imports before you approve imports in the app.

• What MCP tools does TripBooster expose? Summarize mutating tools that need my confirmation.
• Create drafts for flights and hotels from the same caption; validate both.

Agents should call list_pending_imports and show parsed reservations before you approve them in TripBooster. Only run Gmail sync or email import when you explicitly ask.

Is TripBooster preinstalled in ChatGPT or Claude?

No. You add TripBooster as a custom MCP connector (or use OAuth from a client that supports remote MCP). Sign in with your TripBooster account when the client opens the consent flow.

Will the agent import email without asking me?

TripBooster expects a human in the loop. Agents should use list_pending_imports and show parsed reservations before you approve them in the app. Only run sync_gmail_reservations or import_email when you explicitly want new bookings added.

Can agents upload passport scans through MCP?

Not through TripBooster MCP today. Agents can read trips, reservations, alerts, and tasks, and submit email text via import_email for parsing. Document uploads stay in the TripBooster app or vault UI.

What data can agents see?

Only trips, reservations, wishes, alerts, and tasks in your TripBooster account—scoped to OAuth or API key permissions. Agents do not receive your Gmail password; Gmail sync uses connections you enable in Settings → Import.