AI agent
MCP Server + TripBooster
Technical reference for TripBooster MCP
One HTTP MCP endpoint powers every agent page. Connect at tripbooster.dev/mcp with OAuth; API keys live under Settings → Developer.
Example chat
via TripBooster MCP · MCP Server
MCP reads and writes map to the same UI you use in the dashboard.
How to connect MCP Server
- Add only the server URL to OAuth-capable clients: https://tripbooster.dev/mcp
- Client discovers protected-resource metadata and opens TripBooster consent.
- Legacy clients may use Authorization: Bearer with a developer API key from Settings → Developer.
- Call tools/list after connect; mutating tools respect workspace role and idempotency keys.
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.
What you can do with MCP Server
OAuth 2.1
Supabase-backed authorization with browser consent—no Gmail passwords in MCP.
Tool surface
Trips, reservations, wishes, alerts, tasks, Gmail sync, and import_email.
Prompts
Built-in prompts: .
Safety
Parsed imports still need your approval in the app; Gmail sync and import_email require idempotency keys and human intent.
MCP tools
Trips and reservations
list_trips · get_trip · list_reservations · list_wishes
Briefings and tasks
get_daily_summary · get_alerts · get_tasks
Import and review
sync_gmail_reservations · import_email · list_pending_imports
OAuth discovery and API keys are documented under Settings → Developer in the TripBooster app. Public endpoint: https://tripbooster.dev/mcp (not /api/mcp in connector snippets—use the canonical URL above).
Example prompts
- Read list_trips and get_daily_summary resource for my workspace and summarize voice rules.
- Explain idempotency requirements for import_email.
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.
- Where is OAuth documented?
- See Settings → Developer in TripBooster for OAuth and API keys for discovery URLs, environment variables, and verification curl commands.
- What protocol versions are supported?
- The endpoint negotiates MCP initialize versions and supports stateless HTTP discovery per current MCP specs. API keys in query strings are deprecated in favor of Authorization headers.