Tripdremo AI connection guide Version: 1 — 12 November 2026 Onboarding: https://tripdremo.com/en/connect-ai Goal Connect the current AI host to Tripdremo, verify the connection, then continue the traveller's original trip request. Do not replace that request with generic travel advice. Preserve the user's wording and resume it after setup or sign-in. First identify the real host Inspect the tools and integration settings actually available in this environment. Distinguish the user's real AI host from a temporary chat, preview, or code sandbox. A sandbox may be able to read this guide without being allowed to register a durable host integration. Do not claim that Tripdremo is installed, configured, signed in or verified unless the corresponding native setup and tool calls succeed. Never ask the traveller to paste raw JSON, tokens, API keys, authorization codes or OAuth callback URLs into chat. If Tripdremo tools already exist Use the installed Tripdremo integration. Call `tripdremo_auth_status` first. If authentication is required, use the connection's native login flow. Then call `tripdremo_auth_status` again and fetch the schema with `tripdremo_get_plan_schema`. Do not reinstall a working integration. If this host supports remote MCP connections Create a native MCP connection named Tripdremo using: https://mcp.tripdremo.com/mcp This remote service requires Tripdremo login with trips:read and trips:write scopes. Use the real host's native connection and OAuth consent UI. Host UI labels can vary slightly by release; use the equivalent native custom-MCP or connector controls. When the host asks for an authentication method, select OAuth. If it offers client registration choices, select "Register automatically (DCR)". Do not select "Use the provider's published identity (CIMD)": Tripdremo's authorization server supports dynamic client registration, not CIMD. ChatGPT: open Plugins, choose Add custom MCP, create the connection with the URL above, and install it. Use Work mode in ChatGPT and select Tripdremo from the composer's Plugins control or with an @ mention. If the current Chat conversation cannot use custom plugins, open a Work conversation in the same ChatGPT account, carry over the original trip request and this setup prompt, and resume verification there. Do not change AI providers or drop the original trip request. Claude: open Customize, choose Connectors, choose Add custom, enter the URL above, select OAuth and "Register automatically (DCR)" when offered, then activate Tripdremo for the conversation where the original trip request lives. Connector availability depends on the Claude account and plan; do not claim this path is available until the enabled control is visible. If Claude's Add custom connector control is unavailable or disabled, use the marketplace fallback: open Customize, choose Plugins, choose Add marketplace, then choose Add from repository and enter `tripdremo/tripdremo-plugin`. Install `Tripdremo connect`, open Connectors, and choose Connect. Claude should open its native Add custom connector flow with the Tripdremo server URL prefilled. Select OAuth and "Register automatically (DCR)" there when offered, then complete Tripdremo sign-in and consent. This fallback still depends on the account exposing the marketplace and plugin controls; verify each control instead of assuming it. If the current assistant cannot register the integration itself, give the exact native creation step for the detected host, wait for that step and any Tripdremo sign-in or consent to finish, then resume the original request. Do not substitute a manual JSON handoff or claim that opening this guide created the connection. After activation, call `tripdremo_auth_status` and `tripdremo_get_plan_schema`. Use the native integration tools already available. Do not request new browser or desktop-control access just to set up Tripdremo. When direct registration is not available, the exact native manual connection step is the supported fallback. If this is Codex or Claude Code without a remote connection yet Prefer the existing Tripdremo plugin if it is already installed. Otherwise install the public marketplace package from: https://github.com/tripdremo/tripdremo-plugin Codex marketplace commands: codex plugin marketplace add tripdremo/tripdremo-plugin codex plugin add tripdremo-connect@tripdremo Claude Code marketplace commands: /plugin marketplace add tripdremo/tripdremo-plugin /plugin install tripdremo-connect@tripdremo The marketplace-installed Claude Code remote profile is named `plugin:tripdremo-connect:tripdremo-connect`. Prefer Claude Code's native `/mcp` authentication UI when the current agent terminal cannot be interactive. In a real interactive terminal, authenticate that installed profile with: claude mcp login 'plugin:tripdremo-connect:tripdremo-connect' This command requires a TTY; a non-interactive invocation can fail even when the profile is installed correctly. Complete browser sign-in and consent through the native flow. Never ask the traveller to paste OAuth callback URLs, authorization codes, or one-time codes into chat. If the host uses saved remote profiles, create a new profile named "tripdremo-connect" pointing to https://mcp.tripdremo.com/mcp. Keep an existing local stdio Tripdremo configuration compatible: do not invent or append a connection ID to its original command arguments. If marketplace installation is unavailable, register remote MCP directly: Codex: codex mcp add tripdremo-connect --url https://mcp.tripdremo.com/mcp Codex sign-in: codex mcp login tripdremo-connect --scopes trips:read,trips:write --oauth-client-registration dcr Claude Code: claude mcp add --transport http --scope user tripdremo-connect https://mcp.tripdremo.com/mcp Claude Code direct-profile sign-in: claude mcp login tripdremo-connect The short `tripdremo-connect` login name applies only to this directly registered fallback. Do not use it for the marketplace-installed `plugin:tripdremo-connect:tripdremo-connect` profile. In a real coding host with filesystem access, also install the standalone skill folder skills/tripdremo-connect from the public repository using the host's skill installer. Copy the complete folder, including references; preserve other skills and MCP entries. Hosted tools provide their workflow instructions to browser clients without requiring a local skill file. The remote connection needs no local Node.js. If tools require a new session or reload, preserve the request, give a continuation instruction, and perform the verification below in the reloaded host. Verify before planning Verification requires both a successful `tripdremo_auth_status` call and a successful `tripdremo_get_plan_schema` call. A copied prompt, opened web page or saved configuration alone is not verification. Report connection errors honestly and use the host's normal retry or repair flow instead of claiming success. Continue the original trip request Ask only for trip details missing from the user's original request. Follow the live schema exactly. Author the full itinerary locally with this AI; do not silently use paid or backend-AI generation. Save protocol — branch by the tools actually available 1. Fetch the live schema with `tripdremo_get_plan_schema`. 2. Author and validate the complete trip JSON against it locally. 3. Show a short summary and disclose that Tripdremo will store the itinerary and anyone with its share link can read it. The copied prompt explicitly asks to save and return a link, so that request is already consent to save. Ask for confirmation only when the traveller did not request saving or a Tripdremo link. 4. If `tripdremo_prepare_submission` is available, this is the remote flow. Call it with `{request}` and retain its returned `submission_id`. Call `tripdremo_submit_plan` with that `submission_id`, the exact original `request`, schema version, and authored plan. 5. On a transient remote failure, retry the same `submission_id` with the exact same payload. Never change a payload while reusing its ID. 6. On `needs_revision`, repair the plan from the structured issues, call `tripdremo_prepare_submission` again, and submit the newly returned ID. 7. When a remote outcome is unknown, call `tripdremo_submission_status` with the existing ID before preparing anything new. Return only the share link from a confirmed successful save. 8. If `tripdremo_prepare_submission` is not available but `tripdremo_submit_plan` is, use the existing local stdio flow: call `tripdremo_submit_plan` directly with the exact request, schema version, and plan. Do not invent a preparation ID; the local plugin preserves its own compatible idempotency behavior. Do not hand raw trip JSON to the traveller as a manual setup step. If the connection cannot be established, keep the original request intact, state the exact native connection step or blocker, link the onboarding page above, and resume only after the real host exposes verified Tripdremo tools. Privacy and control Never request passwords, payment details, API keys or one-time codes in chat. Do not access email, calendars, files or other accounts without separate permission. Omit sensitive personal details from saved itineraries. Approval applies only to the client and scopes shown in Tripdremo's consent screen and can be revoked later at: https://tripdremo.com/en/ai/connections