TripBooster

AI agent

Agents CLI + TripBooster

HTTP and client CLIs—no TripBooster binary

Headless automation uses the same MCP URL. Prefer OAuth in interactive clients; use API keys only where browser login is impossible.

Sign in to TripBoosterConnect Agents CLI

Example chat

Show curl to call list_pending_imports on a draft ID using my API key.
Use POST /mcp with tools/call and your Bearer key; see Settings → Developer for the key format.

via TripBooster MCP · Agents CLI

CLI and HTTP clients update the same drafts as the web app.

How to connect Agents CLI

  1. Claude Code: claude mcp add with SSE transport to the TripBooster URL.
  2. Codex / custom scripts: JSON-RPC POST to /mcp with Bearer API key.
  3. Claude Desktop (legacy): optional local HTTP clients against tripbooster.dev/mcp bridge with TRIPBOOSTER API key from Settings → Developer.
  4. Never commit API keys; rotate keys in Settings → Developer if leaked.
TripBooster MCP server URL
https://tripbooster.dev/mcp
cURL tools/list (API key)
curl -X POST https://tripbooster.dev/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

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 Agents CLI

  • Claude Code

    Interactive terminal sessions with OAuth when available.

  • curl / HTTP

    tools/list and tool calls for debugging integrations.

  • Local bridge

    HTTP clients against tripbooster.dev/mcp for stdio clients that cannot speak remote OAuth directly.

  • No tripbooster-cli

    We do not ship a standalone npm binary named tripbooster—clients speak MCP directly.

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

  • Document the difference between remote MCP OAuth and the Desktop stdio bridge.
  • List environment variables for HTTP clients against tripbooster.dev/mcp.

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.
Is there a TripBooster CLI npm package?
No. Use MCP-compatible clients (Claude Code, Cursor, curl) or the optional HTTP clients against tripbooster.dev/mcp helper for Claude Desktop-style stdio setups.

Other AI agents

Browse all agents →