get_itinerary_dossier — concierge MCP Tool Read-only
get_itinerary_dossier
(get itinerary dossier) is one of 23 tools on the
concierge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_itinerary_dossier from your client
- Claude Code concierge get_itinerary_dossier run in your project directory
- Claude Desktop concierge get_itinerary_dossier ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor concierge get_itinerary_dossier ~/.cursor/mcp.json
- VS Code concierge get_itinerary_dossier .vscode/mcp.json
- Zed concierge get_itinerary_dossier ~/.config/zed/settings.json
- Windsurf concierge get_itinerary_dossier ~/.codeium/windsurf/mcp_config.json
- Cline concierge get_itinerary_dossier ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI concierge get_itinerary_dossier ~/.gemini/settings.json
- Grok concierge get_itinerary_dossier .mcp.json (in your project root)
- ChatGPT concierge get_itinerary_dossier Settings → Connectors → Advanced → Developer mode
- Claude.ai concierge get_itinerary_dossier Settings → Connectors → Add custom connector
- LangChain concierge get_itinerary_dossier pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http concierge https://concierge.iconic-expeditions.com/mcp
Other tools on this server
- search_content
- search_wp_content
- get_content
- get_wp_content
- list_destinations
- get_destination
- get_itinerary
- list_itineraries
- create_itinerary
- generate_itinerary_from_places
- update_itinerary
- delete_itinerary
- add_day
- price_itinerary
- set_itinerary_dossier
- write_itinerary_day_detail
- add_activity
- delete_activity
- get_pricing
- request_verification
- request_bookings
- request_full_service
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.