Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Concierge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search Africa safari destinations, generate day-by-day itineraries, and price expert travel work.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http iconic-expeditions-concierge-mcp https://concierge.iconic-expeditions.com/mcp
# 2 — ask your agent for something these tools do
# search_content, search_wp_content, get_content and 20 more
Concierge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http iconic-expeditions-concierge-mcp https://concierge.iconic-expeditions.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search Iconic Expeditions content across itineraries, activities, destinations, and posts. Flows through the content chain (WordPress -> local cache -> AI fallback), so gaps WordPress doesn't cover are filled with clearly-labeled AI-synthesized results. Each item includes a source field (wordpress | cache | ai).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Content type to search |
| search | string | no | Search keyword |
| per_page | integer | no | — |
Alias of search_content, kept for backwards compatibility. Prefer search_content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | Content type to search |
| search | string | no | Search keyword |
| per_page | integer | no | — |
Fetch a single content item by type and id, walking the content chain (WordPress -> cache). Returns the item with its source.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | — |
| id | integer | yes | Source content id (WordPress post id) |
Alias of get_content, kept for backwards compatibility. Prefer get_content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | — |
| id | integer | yes | Source content id (WordPress post id) |
List destinations from the database, optionally filtered by region or category.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region | string | no | Filter by region name, e.g. 'Matabeleland North' |
| category | string | no | Filter by category, e.g. 'National Park' |
| limit | integer | no | — |
Get full details for a single destination by slug or id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identifier | string | yes | Either a destination id or its URL slug |
Get a full itinerary with all days and activities, sorted by day number and time slot. Public itineraries are readable without a token; private ones require the owning token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | The UUID of the itinerary |
List itineraries created by the Iconic Expeditions concierge, most recent first. Requires a bearer token.
No parameter schema on file.
Create a new (empty) itinerary attributed to the Iconic Expeditions concierge, made public and returned with its share link. Days are created automatically. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Itinerary title, e.g. '7-Day Hwange Safari' |
| num_days | integer | yes | Number of days |
| description | string | no | Optional short description |
| start_date | string | no | Optional ISO date string for day 1, e.g. '2025-06-01' |
Give at least 3 places plus optional traveller preferences and let the AI concierge build a full, bespoke day-by-day itinerary. It mines Iconic Expeditions content for real detail and synthesizes an ORIGINAL plan tailored to the guest (never a copy of a published itinerary). Attributed to the Iconic Expeditions account and made public. Returns immediately with the itinerary id + share link; poll g
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Itinerary title, e.g. 'Highlights of Zimbabwe' |
| places | array | yes | At least 3 place names, e.g. ['Victoria Falls', 'Hwange', 'Mana Pools'] |
| num_days | integer | yes | Number of days for the trip |
| preferences | string | no | Traveller preferences that should shape the plan: pace, interests, budget, travel style |
| language | string | no | Language for day titles, notes, and activity text: 'en' (English), 'ru' (Russian), or 'zh' (Chinese). Defaults to English. |
Update metadata (title, description, dates, public status) on a concierge itinerary. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
| title | string | no | — |
| description | string | no | — |
| start_date | string | no | — |
| is_public | boolean | no | Set false to unpublish the shareable link |
Permanently delete a concierge itinerary and all its days and activities. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
Append an extra day to a concierge itinerary and increment num_days. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
| title | string | no | Optional day label, e.g. 'Drive to Hwange' |
| notes | string | no | — |
Read an itinerary's planning dossier: its legs, month-by-month seasonality, cost model, booking order, field notes and open choices. Public — no token needed. Returns nulls for blocks the itinerary doesn't have; older itineraries have none of them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
Price an itinerary's cost model against a selection: a comfort tier, any per-line choices, a trip length and a traveller count. Returns the per-person line breakdown and the group total. Public — no token needed. Amounts are in minor units. Call get_itinerary_dossier first for the tier and option ids.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
| tier_id | string | no | Defaults to the cheapest tier |
| option_ids | array | no | One entry per cost option group you want to choose in |
| nights | integer | no | Defaults to the cost model's reference length |
| travellers | integer | no | — |
Write the planning layer above an itinerary's day-by-day. Every block is optional — send only the ones you mean to write. Each block you DO send REPLACES that block entirely, so restate it in full: a partial legs list silently deletes the rest of the legs. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
| countries | integer | no | How many countries the route crosses |
| legs | array | no | The route's chapters. Every day must belong to exactly one leg, and legs must not overlap. |
| seasonality | object | no | One row per thing the trip is timed around, scored 0-3 across all twelve months, plus a verdict per month worth arguing about |
| cost_model | object | no | Per-person breakdown lines, amounts per comfort tier, and any per-line choices |
| booking_order | array | no | What to book, in the order it has to happen |
| field_notes | array | no | Visas, certificates, luggage limits, kit |
| choices | array | no | Either/ors deliberately left open for the traveller |
Write 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. Replaces that day's existing narrative and callouts. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
| day_number | integer | yes | — |
| narrative | string | yes | Two or three short paragraphs, separated by blank lines. Plain text, no markup. |
| callouts | array | no | — |
Add an activity to a specific day and time slot (morning/afternoon/evening). Optionally link to a content item using its type and id. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | Parent itinerary UUID |
| day_id | string | yes | The day UUID to add the activity to |
| slot | string | yes | — |
| title | string | yes | Short title for the activity |
| description | string | no | — |
| duration_minutes | integer | no | — |
| wp_content_type | string | no | Content type to link |
| wp_content_id | integer | no | Source content id |
Remove an activity from a concierge itinerary day. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | string | yes | — |
List the paid concierge service tiers and their prices: itinerary verification, verification + full booking, and full guided service. Read-only and public — use this to quote a traveller before they buy.
No parameter schema on file.
Start a PAID itinerary verification. Our travel experts manually confirm availability, seasonality, routing and current lodge rates, then return a feasibility report and final price. Returns a Stripe checkout URL. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
| contact_email | string | no | Where to send the report + receipt |
| notes | string | no | Anything the experts should know (dates, group size, budget) |
Start a PAID booking service: verification PLUS we make all the bookings (lodges, transfers, activities, permits). Returns a Stripe checkout URL. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
| contact_email | string | no | — |
| notes | string | no | — |
Start a PAID full-service, fully-guided expedition with Iconic Expeditions guides. This $500 is a deposit; the final custom price is quoted by an expert afterward based on the itinerary. Returns a Stripe checkout URL. Requires a bearer token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| itinerary_id | string | yes | — |
| contact_email | string | no | — |
| notes | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Concierge or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Concierge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.