The e-concierge,
as an agent.
art’otel already promises guests a “curated gateway into the art’otel world, here to help you explore, book, and elevate every moment of your stay.” This is that promise as something ChatGPT and Claude can actually call: 20 tools over the real collection — 7 properties, 44 room types and 26 live offers read from artotel.com — ending in a real booking link on Radisson’s own engine.
Connector URL →The collection

art’otel Amsterdam

art’otel Berlin Mitte

art’otel Cologne

art’otel London Battersea Power Station

art’otel London Hoxton

art’otel Rome Via Veneto

art’otel Zagreb
Every photograph, room dimension, offer and property code above was read from
artotel.com by scripts/fetch-artotel.ts — the schema.org Hotel block on each hotel page, the
room pages’ own “Sleeps 2 · King bed · approx 24 m²”, the offer grids, and the hotelCode options in
art’otel’s own booking widget. Last read
2026-08-23. Photography is served from this origin, never hotlinked.
Connect it
https://artotel-concierge.demos.42a.ai/mcp # MCP — everything about the collection, no token
https://artotel-concierge.demos.42a.ai/mcp?token=artotel_user_demo # …plus the account, the composer and the concierge
https://artotel-concierge.demos.42a.ai/openapi.json # ChatGPT Custom GPT Actions
https://artotel-concierge.demos.42a.ai/tools.json # the tool surface, as JSON
In ChatGPT: Settings → Connectors → Add, paste the MCP URL. In Claude: Settings → Connectors → Add
custom connector. Header-less clients can pass ?token= instead of a bearer header.
What it can do
find_artotel
get_hotel
browse_rooms
compare_hotels
list_destinations
list_offers
explore_art
find_dining
get_local_area
explain_policies
check_availability
plan_event
get_my_account
get_my_stays
compose_stay
start_booking
concierge_request
merchant_set_banner
merchant_get_banner
merchant_clear_banner
The components
Eleven rendered components, each self-contained and each rendering in ChatGPT (Apps SDK) and Claude (MCP Apps). Previews with real data:
What it does not do
No rates. art’otel publishes none — they are live on Radisson’s engine and move by
date — so nothing here quotes one, and no schema has a field for a model to fill. What the concierge does instead is
build the real booking link for the property, the dates and the party, using the same property code artotel.com’s own
widget posts, so the first thing the guest sees is the actual price.
No payment, no held rooms, no cancellations. The booking becomes real on Radisson’s secure page,
under the guest’s own eyes. The account, stays and concierge tickets in the demo are synthetic; connect a real
Rewards account and everything downstream is unchanged.
Also here: /journeys — every conversation grouped by what the guest was
actually trying to do, which is what the required stay_goal argument buys.
/stats · /healthz