AI agent
Codex + TripBooster
Chained, scripted agent workflows
Codex excels at multi-step tasks you can rerun. TripBooster is the importing reservations layer; Codex is the orchestrator—not a replacement for your approval.
Example chat
via TripBooster MCP · Codex
Codex can pull performance data before proposing the next run.
How to connect Codex
- Configure Codex to use remote MCP with the TripBooster server URL (OAuth preferred).
- Sign in to TripBooster when the client opens the browser consent flow.
- Store idempotency keys in your scripts when calling import_email or import_email.
- Never embed import_email in unattended cron jobs without a human review step.
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 Codex
Repeatable pipelines
Encode discover → draft → validate → present schedule as a Codex task you run after each content meeting.
Contrast with chat-only
Unlike one-off ChatGPT chats, Codex can reopen the same workflow against your repo and MCP config.
API key fallback
Headless environments can use Bearer API keys against /mcp when OAuth browsers are unavailable.
Audit-friendly
Mutating MCP calls are audited in your workspace; Codex steps should log what it scheduled for you.
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
- Retry failed outputs on post ID … using retry_post after I paste the UUID.
- Refresh metrics for yesterday’s publication and summarize deltas.
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.