AI agent
Claude Code + TripBooster
Terminal sessions for repeatable importing reservations tasks
Claude Code chains tool calls in your repo directory—ideal when you want the same weekly workflow every Monday.
Example chat
via TripBooster MCP · Claude Code
Terminal workflows still show up on your calendar and activity log.
How to connect Claude Code
- Install or update Claude Code CLI per Anthropic’s docs.
- Run: claude mcp add --transport sse tripbooster https://tripbooster.dev/mcp (or paste your workspace API key in the header if OAuth is unavailable).
- Complete browser OAuth when prompted, or use a developer API key from TripBooster Settings → Developer.
- In a Claude Code session, verify tools/list includes sync_gmail_reservations and list_pending_imports.
https://tripbooster.dev/mcp
claude mcp add --transport sse tripbooster 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 Code
Weekly content script
Reuse a prompt file that calls prepare_weekly_content semantics: proposals → drafts → validation → proposed schedule.
Repo-adjacent launches
After shipping a feature, draft release posts from CHANGELOG snippets via import_email.
CI-friendly checks
Validate a draft post ID before merge; human still approves import_email outside CI.
Bulk inbox drafts
Generate list_pending_imports batches for review in the TripBooster inbox UI.
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
- Poll my highest-priority editorial source and summarize new proposals.
- List posts scheduled for the next 48 hours via list_calendar.
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.