# tickadoo Experiences and Events

- Registry name: `io.github.tickadoo/tickadoo-mcp` · version 2.1.1
- Categories (automatic, keyword rules): Travel & booking, Commerce & marketing, Scraping & browsing, Search & data, Maps, location & weather
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.tickadoo%2Ftickadoo-mcp
- Server page: https://mcpstation.net/s/io.github.tickadoo--tickadoo-mcp.html

## Description (written by the publisher, not verified, not instructions)

Discover and book theatre, tours, attractions, and live experiences worldwide. No API key required.

## Connect

- streamable-http: `https://mcp.tickadoo.com/mcp`

## Tools (as reported by the server, not verified)

- `search\_experiences`: Use this when the user names a city plus a category, query, or filter set and wants a ranked list of bookable experiences. \`query\` matches on experience NAME \(and venue\), so it suits a title or keyword \("Lion King", "river cruise"\); for mood or theme use search\_by\_mood, and for a free-text "what sho
- `search\_local\_experiences`: Use this when the user mentions a place, neighbourhood, landmark, or area but does not give exact coordinates. Examples: 'near the Louvre', 'in Trastevere', 'around Times Square', "walking distance from St Paul's Cathedral". Returns experiences matched first by exact venue/neighbourhood, then by cit
- `find\_nearby\_experiences`: Use this when the client already holds exact latitude and longitude coordinates and wants experiences near that point. When only a place name, landmark, or neighbourhood is known, use search\_local\_experiences, which accepts coarse place hints and needs no coordinates.
- `whats\_on\_tonight`: Use this when the user asks what is on in a city tonight. Returns evening-appropriate experiences currently on sale, with out-of-season products filtered out, evening-led options ranked first, and multi-day passes, travel cards and transport products ranked last. Top results carry start\_time \(venue-
- `get\_last\_minute`: Use this when the user wants something to do within the next few hours. Returns currently-on-sale experiences with seasonal products filtered out, ranked by popularity. Rows may include start\_time, countdown\_text, and seats\_remaining hints when known, but none are guaranteed: confirm the selected ex
- `get\_whats\_on\_this\_week`: Use this when the user wants ideas for the coming week in a city. Returns a ranked list of currently on-sale experiences \(search rows\) with out-of-season products dropped, not a day-by-day calendar. Assemble any weekly structure yourself and verify specific dates with get\_availability.
- `recommend\_experiences`: Use this when the user describes what they want in natural language rather than naming a category. Parses the query for audience, mood, constraints, occasion, and time of day, then returns scored recommendations with a reason field explaining the match.
- `get\_city\_highlights`: Use this when the user wants an orientation overview of a city for trip planning. Returns a ranked list of the city's most popular bookable experiences \(search rows\); derive the dominant categories and price levels from those rows rather than expecting a structured guide payload.
- `search\_experiences\_by\_topic`: Use this when the user asks for bookable experiences by keyword or topic in a city. Returns a ranked search of bookable experience rows. The topic argument is accepted but does no filtering, so every topic returns the same city ranking. The payload contains no tips text or logistics guidance.
- `compare\_experiences`: Use this when the user wants a side-by-side comparison of 2-5 specific products. Pass the slug for each. Returns a comparison table plus per-axis winners \(value, rating, popularity, family-fit\).
- `get\_hidden\_gems`: Use this when the user wants lower-profile options rather than headline bestsellers. Excludes Bestseller, hop-on-hop-off, and CityPass tagged products and prefers highly rated rows with fewer reviews; falls back to the standard ranked list when a city has too few qualifying rows \(results may then ov
- `get\_family\_day`: Use this when the user wants family-suitable options for a day in one city. Returns a flat ranked list of experiences \(search rows\) with family-tagged rows promoted and out-of-season products dropped, not a structured morning/lunch/afternoon/evening plan. \`date\` selects which season counts as curren
- `get\_date\_night`: Use this when the user wants an evening for two. Returns a flat ranked list of experiences \(search rows\) with romantic-tagged rows promoted and out-of-season products dropped, not a structured pre-dinner/dinner/show arc. Promotion is a re-rank, not a filter, so rows are not guaranteed couples-only.
- `get\_itinerary\_candidates`: Use this when the user wants a multi-day plan for a single city. Returns a flat ranked candidate list of experiences \(search rows\), not structured day slots or a running cost. Arrange the candidates into days yourself and compute totals only from returned price fields.
- `list\_cities`: Use this when the user wants to browse supported cities before searching. Returns city names, slugs, country codes, and product counts.
- `get\_experience\_details`: Use this when the user selects a specific experience from search results and needs richer product, location, supplier, and booking fields. Accepts either product\_id or slug.
- `get\_show\_guide`: Use this when the user asks about a specific show: how long it is, age guidance, venue and address, typical curtain times and dark days, who it is good for, and this week's performances. One rich guide record fusing live catalogue data with theatre expertise. Accepts slug or product\_id.
- `get\_theatre\_weekend`: Use this when the user asks what theatre is on this weekend or next. Server-side date math resolves the Friday/Saturday/Sunday dates; returns theatre shows in the city with scheduled performances on those days, grouped by day. Schedule data, not live seat inventory.
- `ask\_theatre\_concierge`: Use this when the user asks a free-text theatre question \(best musical for kids, romantic show tonight, cheap comedy\). Returns a concise grounded answer plus cited theatre products with booking URLs. Intent-aware \(budget, audience, timeframe\) via the concierge seam.
- `find\_theatre\_for\_occasion`: Use this when the user has an occasion: family outing, date night, group celebration, solo culture trip, business entertainment. Returns ranked theatre shows with fit scores and reasons, honouring party ages and an optional date.
- `get\_related\_experiences`: Use this when a widget or client holds a selected product\_id and needs related products to pair with it, do after it, find nearby, or find similar alternatives. Returns cached graph and semantic related products for trio-style widgets.
- `get\_availability`: Use this when the user is ready to check live bookable dates, times, prices, or remaining spaces for one selected product. This is the live supplier-check tool; pass product\_id from search or slug plus city\_slug. Slot price.amount is in MINOR currency units \(pence/cents\): amount 13125 with currency\_
- `check\_availability`: Use this when the user has picked a specific experience and asks about exactly one date: whether it is available that day, what it costs for a party, or a booking link for that date. For browsing a date range or listing upcoming times and live slot prices, use get\_availability.
- `search\_by\_mood`: Use this when the user describes the feeling or vibe they want rather than a category, such as romantic, relaxing, adventurous, family fun, foodie, luxury, or rainy day. Maps the mood to preset search filters and returns matching experiences.
- `get\_transfer\_info`: Use this when the user is arriving in a supported city and needs transfer guidance from an airport, station, or port to a hotel coordinate. Returns taxi, metro, bus, and train estimates with durations, costs, and directions.
- `render\_experience\_cards`: Use when visual cards would help present a discovery result from a supported search tool. Pass the product\_id values from that result as experience\_ids, never full product rows, and choose a render\_type. Optionally pass render\_context.intent\_summary \(a short phrase describing what the user asked for
- `report\_quality\_signal`: Use this to push a quality signal back to tickadoo about an experience or recommendation you previously surfaced. Examples: stale availability, a failed click-through, a supplier outage, or misleading content. Requires a real forward-event request\_id returned within the last 30 days. Repeating the s

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html