TripBooster

AI agent

Claude Cowork + TripBooster

Review drafts with your team before scheduling

Use Cowork sessions to align on copy and timing. The agent prepares TripBooster drafts; humans approve sync_gmail_reservations and import_email.

Sign in to TripBoosterConnect Claude Cowork

Example chat

Our Cowork session needs three draft posts for next week—validate each and post a summary table for the team to approve times.
Three drafts created and validated. Summary table ready with proposed slots; I will not schedule until someone in the thread confirms.

via TripBooster MCP · Claude Cowork

Your team reviews the same drafts inside TripBooster before they go live.

How to connect Claude Cowork

  1. Connect TripBooster MCP in your Claude Cowork environment using the remote MCP URL (same OAuth flow as Claude).
  2. Sign in to TripBooster and grant access to the shared workspace your team uses.
  3. In Cowork, assign roles: one person owns final approval for import_email.
  4. Share example prompts so everyone uses list_pending_imports before scheduling.
TripBooster MCP server 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.

What you can do with Claude Cowork

  • Shared review queue

    List draft posts and walk through validation errors as a group before fixing copy in update_post.

  • Approval handoff

    One teammate drafts with import_email; another confirms sync_gmail_reservations after reading list_pending_imports output.

  • Brand guardrails

    get_daily_summary and list_editorial_rules keep Cowork suggestions aligned with workspace policy.

  • Inbox triage together

    Use list_pending_imports for suggested responses; only import_email after explicit team approval.

TripBooster MCP tools

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.

Example prompts

  • Draft replies for the top five NEEDS_HUMAN inbox threads—draft only, no send.
  • Compare last week’s get_daily_summary to our content pillars and suggest two proposal topics.

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.

Frequently asked questions

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.

Other AI agents

Browse all agents →