Content Tools
iconic-expeditions.com
Provides content search and retrieval for Iconic Expeditions, including itineraries, destinations, and posts.
ENDPOINT 1
https://concierge.iconic-expeditions.com/mcp
MCP server metadata
- Name
- iconic-concierge
- Version
- 2.0.0
Known tools 23
search_contentSearch Iconic Expeditions content across itineraries, activities, destinations, and posts.
Inferred read-onlyget_contentFetch a single content item by type and id, walking the content chain (WordPress -> cache).
Inferred read-onlylist_destinationsList destinations from the database, optionally filtered by region or category.
Inferred read-onlyget_itineraryGet a full itinerary with all days and activities, sorted by day number and time slot.
Inferred read-onlylist_itinerariesList itineraries created by the Iconic Expeditions concierge, most recent first.
Inferred read-onlycreate_itineraryCreate a new (empty) itinerary attributed to the Iconic Expeditions concierge, made public and returned with its share link.
Potential side effectsgenerate_itinerary_from_placesGive at least 3 places plus optional traveller preferences and let the AI concierge build a full, bespoke day-by-day itinerary.
Inferred read-onlyupdate_itineraryUpdate metadata (title, description, dates, public status) on a concierge itinerary.
Potential side effectsdelete_itineraryPermanently delete a concierge itinerary and all its days and activities.
Potential side effectsget_itinerary_dossierRead an itinerary's planning dossier: its legs, month-by-month seasonality, cost model, booking order, field notes and open choices.
Inferred read-onlyprice_itineraryPrice an itinerary's cost model against a selection: a comfort tier, any per-line choices, a trip length and a traveller count.
Inferred read-onlyset_itinerary_dossierWrite the planning layer above an itinerary's day-by-day.
Potential side effectswrite_itinerary_day_detailWrite one day out at length — why it is shaped this way, what its timing depends on, what the alternatives cost — plus up to three callouts.
Potential side effectsadd_activityAdd an activity to a specific day and time slot (morning/afternoon/evening).
Inferred read-onlyget_pricingList the paid concierge service tiers and their prices: itinerary verification, verification + full booking, and full guided service.
Inferred read-onlyrequest_bookingsStart a PAID booking service: verification PLUS we make all the bookings (lodges, transfers, activities, permits).
Inferred read-onlyrequest_full_serviceStart a PAID full-service, fully-guided expedition with Iconic Expeditions guides.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.iconic-concierge]
url = "https://concierge.iconic-expeditions.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"iconic-concierge": {
"type": "http",
"url": "https://concierge.iconic-expeditions.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: iconic-concierge
Remote MCP URL: https://concierge.iconic-expeditions.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"iconic-concierge": {
"url": "https://concierge.iconic-expeditions.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"iconic-concierge": {
"type": "http",
"url": "https://concierge.iconic-expeditions.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "iconic-concierge",
"transport": "streamable-http",
"url": "https://concierge.iconic-expeditions.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for iconic-expeditions.com was fetched 2026-08-24T08:20:01.316Z.
iconic-expeditions.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.