list_destinations — concierge MCP Tool Read-only
list_destinations
(list destinations) 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 list_destinations from your client
- Claude Code concierge list_destinations run in your project directory
- Claude Desktop concierge list_destinations ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor concierge list_destinations ~/.cursor/mcp.json
- VS Code concierge list_destinations .vscode/mcp.json
- Zed concierge list_destinations ~/.config/zed/settings.json
- Windsurf concierge list_destinations ~/.codeium/windsurf/mcp_config.json
- Cline concierge list_destinations ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI concierge list_destinations ~/.gemini/settings.json
- Grok concierge list_destinations .mcp.json (in your project root)
- ChatGPT concierge list_destinations Settings → Connectors → Advanced → Developer mode
- Claude.ai concierge list_destinations Settings → Connectors → Add custom connector
- LangChain concierge list_destinations 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
- get_destination
- get_itinerary
- list_itineraries
- create_itinerary
- generate_itinerary_from_places
- update_itinerary
- delete_itinerary
- add_day
- get_itinerary_dossier
- 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.