MCP is the authority
The remote server authenticates you and provides private data, validation, and actions.
Connect Trip Planner
Connect the standard MCP server for private Trip Plan data and actions. Then, if you want, add portable skills that teach your agent how to plan with it well.
The remote server authenticates you and provides private data, validation, and actions.
Portable instructions improve planning and research. They do not install MCP, grant access, or hold your Trip Plan.
Add this production endpoint as a remote MCP server in your agent, then complete secure sign-in in the browser.
https://hardy-goldfish-323.convex.site/mcpChoose where the optional guidance belongs. Codex is tested for every release; other standards-conforming skill hosts are supported on a best-effort basis.
npx skills add bustakar/trip-planner-skills --agent codexRun this after connecting MCP. For Other agent, the interactive installer asks you to choose a supported host. Project scope is the installer default; global scope adds -g.
What varies by agent: menu names, activation, and interactive widgets. The MCP tools and structured plan remain the same; identical widget rendering is not promised.
For a reproducible manual install, download the versioned archive and verify its published SHA-256 checksum before extraction.
The versioned public release contains both portable skills and a file manifest.
Download archive ↗Keep the archive and checksum file in the same directory.
shasum -a 256 -c SHA256SUMS
unzip trip-planner-skills-1.0.0.zip
npx skills add ./trip-planner-skills-1.0.0Most setup problems come from stale discovery data or an unfinished sign-in.
Finish the browser sign-in, return to the agent, and approve the connection. If it expired, start sign-in again.
Confirm the full endpoint ends in /mcp and that the client supports OAuth discovery, CIMD, and remote Streamable HTTP.
Restart the agent or open a new session after installation. Confirm you selected the intended agent and project or global scope.
Disconnect Trip Planner, clear the agent’s cached MCP metadata if supported, then reconnect and start a new session.
Still stuck? Contact support.